Skip to content
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

[Core] Ray's random generated port doesn't exclude already used ports #46453

Open
totoroyyb opened this issue Jul 5, 2024 · 1 comment
Open
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core P1 Issue that should be fixed within a few weeks

Comments

@totoroyyb
Copy link

totoroyyb commented Jul 5, 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.

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.

@totoroyyb 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
@Superskyyy
Copy link
Contributor

I will fix that.

@anyscalesam anyscalesam added the core Issues that should be addressed in Ray Core label Jul 8, 2024
@jjyao 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't core Issues that should be addressed in Ray Core P1 Issue that should be fixed within a few weeks
Projects
None yet
Development

No branches or pull requests

4 participants