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
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
The text was updated successfully, but these errors were encountered:
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 thecluster_name
, reusing the existing instance. [Fixed in Fix Azure restarting existing instance with different cluster_name #111 ]ray up
commend is finished, it sometimes takes a while for the cluster to be available forray
, especially for Azure, which will cause theray exec
andray get_head-node-ip
in our code to fail.local ray version: 1.9.0
remote ray version: 1.7.0
The text was updated successfully, but these errors were encountered: