Oh, and I also found some more tiny bugs.
-
Consider this situation: we have a pool, all workers are busy and there is a queue of waiting callers. Then pool receives a call to create more idle workers, but these workers won’t be returned to waiting callers.
-
And there’s also this nasty bug which is very rare in normal conditions but quite possible in extreme load scenario. Caller sits in get_idle_worker, then timeout expires, caller sends the
cancel_waitingand before Poolex receives the cancel message, some worker becomes available and gets sent to this waiting caller. Then Poolex will handle thecancel_waitingmessage and we’ll have a worker which is considered busy, but caller may never use it and this worker will be busy until caller dies
