a0259e6b14
The custom thread_pool could not restart in certain cases due to limitations with python threads. This moves to using multiprocessing.dummy for the thread pool and gevent to allow thread timeouts. Also cleans up some of the asynchronous logic. Pools have constant numbers of threads, so thread count is checked at pool creation No longer tracks job start time, as this is handled by timeouts. Move resultsq instantiation so pool restart does not drop data. Mark checks as done at end of run rather than when results are processed. Closes-Bug: 1446757 Change-Id: I28bdd8d8404087097bff9f93ff60f5cc86a72fbb |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| jmxfetch-0.3.0-jar-with-dependencies.jar | ||
| jmxterm-1.0-DATADOG-uber.jar | ||