Improve the logs before creating the ray cluster #2316
+18
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrewsykim
reviewed
Aug 20, 2024
KPostOffice
reviewed
Aug 26, 2024
oksanabaza
force-pushed
the
kuberay-logs
branch
2 times, most recently
from
1ba5f5d
to
9f67eae
Compare
kevin85421
reviewed
Aug 31, 2024
oksanabaza
force-pushed
the
kuberay-logs
branch
from
95e3c5c
to
bd35cf5
Compare
oksanabaza
force-pushed
the
kuberay-logs
branch
from
bd35cf5
to
1979fd5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
Improved logs in case the network is very slow during the Ray cluster creation. Now, if the pods take hours to be created, a message about the status of the pods will appear. ref 2148
Related issue number
Checks