The stop() routine of BalancerCommandsScheduler is currently relying on a "fire&forget" strategy to cancel every outstanding request.

While this minimises the execution time of the method, it exposes the class to potential data races in case remote responses to cancelled requests were still received after destroying the Scheduler.

A more robust alternative consists on synching on the reception of every response during the stop() of the scheduler.