Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
This matters more when the allocation cycle interval is set to large values (e.g. 30 seconds, 1 minute, etc).
When the allocator is paused, the interval timeouts continue but an allocation cycle gets skipped. So, if the interval is long, when it's resumed, it can take up to an entire interval again to have another cycle. E.g. with 1 minute cycle
0mins
1mins: allocate
1.01mins: pause
2mins: allocate skipped
2.01mins: resume
3mins: allocate
In this case, one would expect that resuming at 2.01 mins should just immediately trigger an allocation cycle since we're "overdue" for one, and start the interval timeouts again fresh.