fix queue resumption after modifier reduces counter to 0 #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was noticing an issue where a queue (used for periodic background processing) with a counter that is modified by the cpu regulator would 'freeze' after system cpu went high. My background processes would just stop until jobs was restarted. It turns out that the modifiers values would never reduces after going up, and that if all of my background processors were busy waiting on jobs:ask, nothing would cause jobs_server to allow() them. so I:
a new modifier that is lower can override an old higher modifier
modified counter values are higher than before; if so, revisit queues