-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Fix send()/recv() to adhere to timeout #109611
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/109611
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 601093b with merge base d04b35e ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D49418976 |
|
tried using this on my PP hang. it seems like it partially works (watchdog is picking up on a timeout for a RECV op. However it is giving me this it's suspicious that it says the seq number is 0, as i've already executed a bunch of steps of forward/backward and each step should be waiting on completion of a previous send/recv. |
Summary: Point to point ops don't enqueue their work to the `workMetaList_` which means that the NCCL watchdog does not watch over them, hence they do not respect the collective timeouts. Test Plan: While trying to add a test I found we dont have tests which validate the nccl watch dog. It looks like this is because we dont have a good way to detect when nccl watchdog has thrown an error (exception is thrown in a side thread) in our testing framework / `MultiprocessTestCase` I manually tested this change with the script in pytorch#109401, but need to look more closely at how to automate a test for NCCL watchdog Differential Revision: D49418976
89bb17b to
9a77048
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49418976 |
|
Thanks @wconstab, it does look like sequence # also needs to be updated. That might have also caused the issue with desync debug since it reads the seq #, i will double check it |
9a77048 to
601093b
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49418976 |
|
ok this works for me now-- at least in a trivial case where i intentionally cause a hang, i get a reasonable output from the desync report: |
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.
thanks for fixing @H-Huang
|
@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 |
Summary: Point to point ops don't enqueue their work to the `workMetaList_` which means that the NCCL watchdog does not watch over them, hence they do not respect the collective timeouts. Test Plan: While trying to add a test I found we dont have tests which validate the nccl watch dog. It looks like this is because we dont have a good way to detect when nccl watchdog has thrown an error (exception is thrown in a side thread) in our testing framework / `MultiprocessTestCase` I manually tested this change with the script in pytorch#109401, but need to look more closely at how to automate a test for NCCL watchdog Differential Revision: D49418976 Pull Request resolved: pytorch#109611 Approved by: https://github.com/wconstab
Summary: Point to point ops don't enqueue their work to the `workMetaList_` which means that the NCCL watchdog does not watch over them, hence they do not respect the collective timeouts. Test Plan: While trying to add a test I found we dont have tests which validate the nccl watch dog. It looks like this is because we dont have a good way to detect when nccl watchdog has thrown an error (exception is thrown in a side thread) in our testing framework / `MultiprocessTestCase` I manually tested this change with the script in pytorch#109401, but need to look more closely at how to automate a test for NCCL watchdog Differential Revision: D49418976 Pull Request resolved: pytorch#109611 Approved by: https://github.com/wconstab
Summary: Point to point ops don't enqueue their work to the
workMetaList_which means that the NCCL watchdog does not watch over them, hence they do not respect the collective timeouts.Test Plan:
While trying to add a test I found we dont have tests which validate the nccl watch dog. It looks like this is because we dont have a good way to detect when nccl watchdog has thrown an error (exception is thrown in a side thread) in our testing framework /
MultiprocessTestCaseI manually tested this change with the script in #109401, but need to look more closely at how to automate a test for NCCL watchdog
Differential Revision: D49418976