Allow minion workers to have different priority. #3045
Merged
Conversation
This file contains 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
Minion workers can now specify a higher (or lower) priority which means that notebook queries will be directed to the minions rather than running on the master node. Minion preferences are now set in the config file in a Minion section: ```yaml Minion: notebook_worker_priority: 10 notebook_number_of_local_workers: 2 ``` Allows 2 workers with priority 10 to be running on each minion.
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.
Minion workers can now specify a higher (or lower) priority which means that notebook queries will be directed to the minions rather than running on the master node.
Minion preferences are now set in the config file in a Minion section:
Allows 2 workers with priority 10 to be running on each minion.