[RayService] Revert "Disable async serve handler in Ray Service cluster (#447)" #606
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.
This reverts commit de8e242.
Why are these changes needed?
Ray 2.0 lets users build their Serve deployment graphs using async handles. However, KubeRay disables async handles by default. Once users build their deployment graphs, they attempt to use it with KubeRay but must add code changes to remove double
await
statements used with async handles. See Issue #28908 in the Ray repo for more info.This change removes the logic that disables async handles in KubeRay.
Related issue number
See Issue #28908 in the Ray repo for more info.
Checks