-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[c10d] differentiate timeout errors from nccl errors #138240
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
Conversation
Summary: It's important for c10d to differentiate different reasons of watchdog failures. E.g, timeout vs nccl errors, and let users to handle the errors depends on the type of error Test Plan: UT Subscribers: Tasks: Tags: [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/138240
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 50ac546 with merge base 20af56d ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Skylion007
left a comment
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.
Thank you! This functionality will be really helpful
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
| } catch (...) { | ||
| LOG(ERROR) | ||
| << logPrefix() | ||
| << "Failed to rerieve TORCH_NCCL_DESYNC_DEBUG report with unknown error." |
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.
Can the exception what() be logged here?
Stack from ghstack (oldest at bottom):
Summary:
Our watchdog does not differentiate timeout from NCCL errors clearly in terms of both log and code paths.
It's important for c10d to differentiate different reasons of watchdog
failures. E.g, timeout vs nccl errors, and possibly let users to handle the
errors differently depends on the type of errors
Test Plan:
UT
Subscribers:
Tasks:
Tags:
cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o