Add pool name option to worker pools #1188
Open
Conversation
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
|
This was a great idea, wonder why it never got traction. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 found myself debugging an error in production infrastructure that made some of the DJ workers to die (or not start at all) and I was having a hard time figuring out which of the pool where missing workers.
This PR adds a 3rd optional parameter to the pool specification syntax to add a tag to the processes name that indicates the pool they belong to.
The syntax is
--pool=queue_1:30:a-pool-namethis will spawn 30 processes nameddelayed_job.a-pool-name.{0..29}.If omitted, then it uses the standard naming.