Update invariant for collectives in spawn plugins #11020
Closed
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?
This is minor cleanup after #10896 . Processes are spawned first, then the init distributed connection happens. As a result, this PR removes any ambiguity around these collectives: the invariant is that the distributed connection is set up before the trainer calls them.
This removes the possibility of subtle bugs leading when the Trainer calls
TrainingTypePlugin.barrier()
- if the distributed connection was not initialized, we'd silently pass through, which could lead to synchronization problems later.Part of #7534
Does your PR introduce any breaking changes? If yes, please list them.
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃