You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
keyile opened this issue
Aug 10, 2021
· 4 comments
Labels
bugSomething that is supposed to be working; but isn'tstaleThe issue is stale. It will be closed within 7 days unless there are further conversationtriageNeeds triage (eg: priority, bug/not-bug, and owning component)
It could be a deadlock when the main thread (holding GIL) is waiting for the mutex in core worker, and the heartbeat thread (holding the mutex) is waiting for GIL. We provide the corresponding stacks below to make it more clear:
Ray version and other system information (Python version, TensorFlow version, OS):
Ray: 1.5.0
Python: 3.7.9
OS: Mac OS 11.4
Reproduction (REQUIRED)
The reproduction is very difficult so no code can be provided here.
Please provide a short code snippet (less than 50 lines if possible) that can be copy-pasted to reproduce the issue. The snippet should have no external library dependencies (i.e., use fake or mock data / environments):
If the code snippet cannot be run by itself, the issue will be closed with "needs-repro-script".
I have verified my script runs in a clean environment and reproduces the issue.
I have verified the issue also occurs with the latest wheels.
The text was updated successfully, but these errors were encountered:
keyile
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Aug 10, 2021
To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.
If there is no further activity in the 14 days, the issue will be closed!
If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
If you'd like to get more attention to the issue, please tag one of Ray's contributors.
bugSomething that is supposed to be working; but isn'tstaleThe issue is stale. It will be closed within 7 days unless there are further conversationtriageNeeds triage (eg: priority, bug/not-bug, and owning component)
What is the problem?
It could be a deadlock when the main thread (holding GIL) is waiting for the mutex in core worker, and the heartbeat thread (holding the mutex) is waiting for GIL. We provide the corresponding stacks below to make it more clear:
The PR #12803 may be relative with this issue.
Ray version and other system information (Python version, TensorFlow version, OS):
Ray: 1.5.0
Python: 3.7.9
OS: Mac OS 11.4
Reproduction (REQUIRED)
The reproduction is very difficult so no code can be provided here.
Please provide a short code snippet (less than 50 lines if possible) that can be copy-pasted to reproduce the issue. The snippet should have no external library dependencies (i.e., use fake or mock data / environments):
If the code snippet cannot be run by itself, the issue will be closed with "needs-repro-script".
The text was updated successfully, but these errors were encountered: