-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Ray Core] "/tmp/ray" should not be hard coded for dashboard/observation. #41648
Comments
I think 1~2 days of work... But the team is very overloaded lately. @luxunxiansheng Would you be interested in contribution here? |
@scottsun94 Thanks for reporting the issue! We tried with a local ray cluster setup with I'm wondering if you can help provide more detailed steps to reproduce the issue you are facing? It will be very help for our further investigation!! Also, one thing to note is that, when starting the ray cluster, the default grafana/prometheus configs are generated with |
|
Thanks for the clarification, @scottsun94! And sorry for the mistag. I misunderstood the ask. I'll take a further look. |
What happened + What you expected to happen
When I config the --temp-dir for the ray start , the output does redirect to the new folder. However, the generated artifacts found in the /session/latest/metrics/ are still using the "/tmp/ray " . Ideally all the places once using "/tmp/ray" should be replaced with the new temp-dir.
Versions / Dependencies
ray 2.8
Reproduction script
As described above.
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered: