fix port conflict in parallel dygraph mode #28497
Merged
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.
PR types
Bug fixes
PR changes
Others
Describe
when running dygraph parallel code in local machine, random failure will occur. It may be caused by the port conflict when gloo and nccl initialized at the same time.
rank0 log (send id, connect failed):
rank3 log (receive id, bind failed):
In this PR, we change the order of the gloo and nccl init like below:
HttpServer start -> NCCL init -> GLOO init
HttpServer is used for gloo initial, which will use rank0 port. After changing order, port conflict will be resolved.