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
m-harmonic opened this issue
Jun 6, 2024
· 2 comments
Labels
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoretriageNeeds triage (eg: priority, bug/not-bug, and owning component)
Start a cluster from the command line without a .yaml file:
ray start --head --port=6379 --temp-dir=/tmp/ray
Stop Ray processes manually
ray stop
The cluster file (ray_current_cluster) is still there and has not been cleaned up.
The problem is that starting ray again after this using ray.init() will fail because it sees the existing cluster file and tries to connect to that cluster instead of starting a new local one. Passing address="local" fixes the problem, however.
Versions / Dependencies
Ray: 2.9.3
Python: 3.10.12
OS: Ubuntu 20.04.6 LTS
Reproduction script
ray start --head --port=6379 --temp-dir=/tmp/ray
ray stop
ls /tmp/ray/ray_current_cluster
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered:
m-harmonic
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Jun 6, 2024
bugSomething that is supposed to be working; but isn'tcoreIssues that should be addressed in Ray CoretriageNeeds triage (eg: priority, bug/not-bug, and owning component)
What happened + What you expected to happen
ray start --head --port=6379 --temp-dir=/tmp/ray
ray stop
The problem is that starting ray again after this using
ray.init()
will fail because it sees the existing cluster file and tries to connect to that cluster instead of starting a new local one. Passing address="local" fixes the problem, however.Versions / Dependencies
Ray: 2.9.3
Python: 3.10.12
OS: Ubuntu 20.04.6 LTS
Reproduction script
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered: