-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Remove deprecated torch_distributed_backend
logic
#14693
Merged
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
awaelchli
added
deprecation
Includes a deprecation
breaking change
Includes a breaking change
strategy
labels
Sep 13, 2022
awaelchli
requested review from
tchaton,
justusschock,
kaushikb11,
Borda,
carmocca,
rohitgr7,
otaj and
williamFalcon
as code owners
September 13, 2022 22:19
carmocca
approved these changes
Sep 14, 2022
This was referenced Sep 14, 2022
awaelchli
added a commit
that referenced
this pull request
Sep 14, 2022
Borda
approved these changes
Sep 15, 2022
mergify
bot
added
ready
PRs ready to be merged
and removed
has conflicts
ready
PRs ready to be merged
labels
Sep 15, 2022
otaj
approved these changes
Sep 16, 2022
tchaton
approved these changes
Sep 16, 2022
@@ -171,6 +171,10 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/). | |||
- Removed the deprecated `BaseProfiler` and `AbstractProfiler` classes ([#14404](https://github.com/Lightning-AI/lightning/pull/14404)) | |||
|
|||
|
|||
- Removed the deprecated way to set the distributed backend via the environment variable `PL_TORCH_DISTRIBUTED_BACKEND`, in favor of setting the `process_group_backend` in the strategy constructor ([#14693](https://github.com/Lightning-AI/lightning/pull/14693)) |
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.
I personally would have kept it but otherwise, LGTM !
rohitgr7
pushed a commit
that referenced
this pull request
Sep 24, 2022
* Remove deprecated torch_distributed_backend logic * changelog * mention deprecated * imports Co-authored-by: Jirka Borovec <[email protected]> Co-authored-by: Jirka <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking change
Includes a breaking change
pl
Generic label for PyTorch Lightning package
ready
PRs ready to be merged
strategy
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.
What does this PR do?
Removes distributed backend logic slated for removal in 1.8.
Does your PR introduce any breaking changes? If yes, please list them.
Yes. The environment variable PL_TORCH_DISTRIBUTED_BACKEND can no longer be used to set the backend (gloo, nccl) and has to be controlled through the code/strategy directly.
resolves #11745
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
I made sure I had fun coding 🙃