-
Notifications
You must be signed in to change notification settings - Fork 871
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
How to trigger several independent communications(e.g allgather) simultaneously? #1607
Comments
The particular error you're seeing ( Creating non-overlapping communicators and running simultaneous collective operations on them is well supported in NCCL. We would need more context to understand what triggers the problem in your case. The small excerpt of the |
@kiskra-nvidia Thank you very much for your reply. Error log:
Implementation:
Comm function:
|
It's still not enough NCCL output to tell for sure but my guess is that the communicators are not being initialized properly. Most likely a stale ncclUniqueId is being used (i.e., the value is not being updated/propagated correctly for different communicators). Whether that's due to a problem in your code or in PyTorch, I don't know. My recommendation would be to ask the PyTorch community for help... |
@kiskra-nvidia Thank you for your response. Does this mean that the issue should be due to a bug in the code (incorrect NCCL call) rather than the communication backend not allowing two independent communications? I will try to submit the issue to the PyTorch community. |
Yes, my suspicion is that the bug is in a software layer above NCCL -- whether in PyTorch or in the app, I can't tell. |
For example, in training with 4 GPUs, I divide the GPUs into pairs and create two communication groups: group1 = dist.new_group([0, 1]) and group2 = dist.new_group([2, 3]). If I want to run independent dist.all_gather operations within both communication groups simultaneously, it results in an error. I'd like to ask how to implement this correctly.
The text was updated successfully, but these errors were encountered: