Allow selecting which celery worker(s) to ping #370
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
sevdog
force-pushed
the
celery-worker-name
branch
from
0a29784 to
495bd98
Compare
sevdog
force-pushed
the
celery-worker-name
branch
from
30ff193 to
c4d03f3
Compare
sevdog
force-pushed
the
celery-worker-name
branch
from
fefb40e to
af987cc
Compare
sevdog
force-pushed
the
celery-worker-name
branch
from
af987cc to
b4b03ee
Compare
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.
This PR aims to add the ability to select which celery worker needs to be ping-ed.
The main use case is to use the management command to check a specific worker, thus the check should be ok only if that worker is up&running. Since celery
app.control.pingallows a list as parameter the settings allows a list too. By default it was keptNonesince it means "ping every worker", which is the current behaviour.