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
Starting ray instance with ray start ... without specifying the port number can lead to port conflicts. It looks like the randomly generated port numbers conflict with the worker ports. Ray internal port number random generation should exclude these used ports.
ValueError: Ray component worker_ports is trying to use a port number 18203 that is used by other components.
Port information: {'gcs': 'random', 'object_manager': 'random', 'node_manager': 'random', 'gcs_server': 'random', 'client_server': 10001, 'dashboard': 8265, 'dashboard_agent_grpc': 53136, 'dashboard_agent_http': 52365, 'dashboard_grpc': 'random', 'runtime_env_agent': 62091, 'metrics_export': 18203, 'redis_shards': 'random', 'worker_ports': '9998 ports from 10002 to 19999'}
Versions / Dependencies
ray, version 2.31.0
Reproduction script
Just any ray start can potentially cause this issue
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered:
totoroyyb
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Jul 5, 2024
jjyao
added
P1
Issue that should be fixed within a few weeks
and removed
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Jul 8, 2024
What happened + What you expected to happen
Starting ray instance with
ray start ...
without specifying the port number can lead to port conflicts. It looks like the randomly generated port numbers conflict with the worker ports. Ray internal port number random generation should exclude these used ports.Versions / Dependencies
ray, version 2.31.0
Reproduction script
Just any
ray start
can potentially cause this issueIssue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered: