-
Notifications
You must be signed in to change notification settings - Fork 334
Fallback to python task if worker is zero for pytorch #1629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two questions:
workers=0separately inget_customsince in this case we don't want to create aPytorchJob. (See how this is done for elastic task below)task_config=Pytorch(workers=0)is equivalent to notask_configat all. However,torch.distributed.init_process_group()will not work without the env vars set by the operator. We could solve this by overwriting theexecutemethod and simply setting the env varsWORLD_SIZE=1,RANK=0, and potentially the master address (would have to try whether it is required).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you y'all think about throwing an error if workers=0 and telling people to use a standard python config if they want to run it on a single machine?
If people really want to set workers to 0 then I understand having a smooth fallback, but otherwise it could confuse people if they make a mistake.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ByronHsu @wild-endeavor the new pytorch elastic task can run locally and in a single k8s pod but also with multiple workers using kubeflow training operator. I'd say its functionality is a superset of the already existing
PyTorchtask config. What do you think about using this one in order to debug dist training with a single worker @ByronHsu ?I think falling back to a normal pod (without kubeflow operator) when doing
task_config=PyTorch(num_workers=0)doesn't make much sense because the env vars likeMASTER_ADDR,RANK, ... required bytorch.distributed.init_process_group(), ... will not be set, neither by the kubeflow operator, nor by the pytorch task logic and distributed training, thus, cannot be tested.I would propose to either allow
num_workers=0inPyTorchtask but use kubeflow training operator also in this case (when users don't want to use the training operator, they can useElastic) or 2) not allownum_workers=0as is the case now.