Closed
Description
ThreadPoolExecutor
with min and max thread count (but with unlimited queue) should work better than the current fixed size thread pool executor:
- On startup all primary resources are reconciled, in this phase a controller might need more threads to handle the spike.
- The thread pool should not be unlimited, so for example on startup does not create too much threads.
- Unlimited queue is needed since we don't want to drop triggering of a reconciliation, the size of this queue is already bounded by the number of the primary resources (this logic is handled by
EventProcessor
)