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

Problems of Azure related to ray bug #110

Closed
1 of 2 tasks
Michaelvll opened this issue Dec 16, 2021 · 2 comments
Closed
1 of 2 tasks

Problems of Azure related to ray bug #110

Michaelvll opened this issue Dec 16, 2021 · 2 comments
Assignees

Comments

@Michaelvll
Copy link
Collaborator

Michaelvll commented Dec 16, 2021

The Azure is now usable, though there are two problems related to ray that needs to be further investigated:

  • ray up for Azure will ignore the cluster_name, reusing the existing instance. [Fixed in Fix Azure restarting existing instance with different cluster_name #111 ]
  • After ray up commend is finished, it sometimes takes a while for the cluster to be available for ray, especially for Azure, which will cause the ray exec and ray get_head-node-ip in our code to fail.

local ray version: 1.9.0
remote ray version: 1.7.0

@romilbhardwaj
Copy link
Collaborator

@Michaelvll can we close this issue?

@Michaelvll
Copy link
Collaborator Author

Yes, we have not observed the problem mentioned for a long time. Maybe we can close this issue now. Please raise another issue if this happens again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants