-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Probable race condition #7617
Comments
Can you try this on latest master https://ray.readthedocs.io/en/latest/installation.html#latest-snapshots-nightlies ? This bug might be fixed by 46953c5 |
I tried on master: no more errors about KeyError, but now there is issue about "the local object store is full":
and several times i saw this message in logs. Store never be cleaned. I don't know if this connected with my code example, or something bad happens in master. Looks like my code is pretty straightforward. |
@almln I was able to run it with cc @stephanie-wang @edoakes looks like some objects are refs not cleaned up or gc'ed in this use case. cc @ijrsvt i found a new bug, can you reproduce it with
|
nvm for the |
What is the problem?
While trying to use ray for image processing pipeline we faced with (probably) race condition. Debug output from ray says:
Seems like thread Dummy-1 (who is this?) make some bad things with Object 276f, and then we unsuccessfully try to use this object as a key.
It may be connected with TODO in _complete_future().
In what way should we think to fix or bypass this issue?
Environment:
Ubuntu 18.04
Python 3.6 (the same on 3.7)
Ray 0.8.2
Reproduction
Heavily truncated version of my code for reproduction:
Reproduction example
The text was updated successfully, but these errors were encountered: