Open Hoeze opened 3 years ago
Hi, I'm a bot from the Ray team :)
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!
You can always ask for help on our discussion forum or Ray's public slack channel.
Is there a solution to this problem yet?
@Hoeze In ray 2.0, we made the previous experimental dashboard the default dashboard. Not sure if you have upgraded to 2.0, but are you still running into this issue with this new dashboard?
Hi @scottsun94, sorry for the late answer. I just tested it with ray v2.0.0 and yes, this is still an issue. => Please keep this issue open :)
@rkooo567 could you take a look?
@Hoeze we completely deprecated redis. So there's no redis password. It is probably just legacy code we haven't cleaned up.
I found it is indeed the legacy code. Let me remove them quickly.
It's the raylet process not the dashboard process that accepts --redis-password
, but we still need to fix it.
What is the problem?
When running ray init in a notebook, it starts a dashboard by passing
--redis-password=<pw>
on the CLI.Ray version and other system information (Python version, TensorFlow version, OS): ray, version 2.0.0.dev0 running on Centos 8 with python 3.8
Reproduction (REQUIRED)
Spawn some ray (single-node) cluster and run the following command:
Fix
The dashboard should obtain passwords (and all other secret variables) via environment variables.