Glenn Sarti f209c2b830 (GH-226) Respond quickly to VMs being consumed ... Previously in commit 9b0e55f959 the looping period was changed from a static number to a dynamic one depending on load, however this meant that the operation to refill a pool was slowed down somewhat. While not a problem under normal loads, when a pool was quickly consumed, the pool manager may not respond quickly enough to refill the pool. This commit: - Changes the sleep method, to us a helper sleep method that will wakeup periodically and evaluate other wakeup events. This could be used later to exist sleep loops when pooler is shutting down to stop blocking threads - By default the wakeup_period is set to the minimum pool check loop time, thus emulating the behaviour prior to commit 9b0e55f959 - Adds tests for the behaviour		2017-09-05 21:41:32 -07:00
..
api	(POOLER-73) Restructure tests to unit and integration directories	2017-02-17 13:04:38 -08:00
providers	(POOLER-89) Identify when config issue is present	2017-08-15 10:58:37 -07:00
generic_connection_pool_spec.rb	(POOLER-52) Add recovery to vSphere connections	2017-05-17 13:52:28 -07:00
pool_manager_spec.rb	(GH-226) Respond quickly to VMs being consumed	2017-09-05 21:41:32 -07:00