[18.0][IMP] queue_job: add pause option on channels - #960
Open
guewen wants to merge 1 commit into
Open
Conversation
Contributor
|
Hi @sbidoul, |
amh-mw
suggested changes
Aug 17, 2026
| self.capacity = config.get("capacity", None) | ||
| self.sequential = bool(config.get("sequential", False)) | ||
| self.throttle = int(config.get("throttle", 0)) | ||
| self.paused = int(config.get("paused", False)) |
Add a new "paused" option on channel configuration. A paused channel is equivalent to a channel with no capacity: it yields no job and also blocks all its subchannels. It still needs a restart of the jobrunner, so it does not allow dynamic pause/resume, but hot reload may be added later in #765. It still is an improvement over setting the capacity at 0, because it keeps the capacity in the configuration (removing the option in the config restores the initial capacity). Also, it does not require changing the channel of a job, which is an issue when resuming paused jobs (they should go back to their former channel to be resumed with their expected properties related to capacity/sequential/throttle).
guewen
force-pushed
the
18.0-queue-job-pause
branch
from
August 18, 2026 05:54
83f72e6 to
621a998
Compare
amh-mw
approved these changes
Aug 18, 2026
sbidoul
approved these changes
Aug 18, 2026
Contributor
|
loving the idea. are we able to pause and got it applied right away or would it require a restart? |
Member
Author
@hoangtrann right now it needs a restart. Trying something with hot reload here #962 it somehow works with caveats but still need some work, and it changes the channel config to be per db instead of global (in my wip, you can choose between the current server-side static config that do not support hot reload or the per db config that supports hot reload). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a new "paused" option on channel configuration. A paused channel is equivalent to a channel with no capacity: it yields no job and also blocks all its subchannels.
It still needs a restart of the jobrunner, so it does not allow dynamic pause/resume, but hot reload may be added later in #765.
It still is an improvement over setting the capacity at 0, because it keeps the capacity in the configuration (removing the option in the config restores the initial capacity).