Doc: gang-scheduling for kubeflow training-operator #3851
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
Signed-off-by: Fabio Grätz <fabiogratz@googlemail.com>
fg91
force-pushed
the
fg91/doc/kubeflow-pluging-gang-sched
branch
from
8600dcb
to
9432c7e
Compare
|
You are a rockstar @fg91 |
3 tasks
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.
Describe your changes
In the Flyte Slack community there have been multiple questions recently how timeout errors can be avoided which occur when the workers of distributed training jobs don't start at the same time due to resource constraints.
The best solution to this problem is to use a Kubernetes scheduler which supports gang scheduling. In this PR I add documentation how this can be configured.