[Serve][Doc] Add Failure Recovery Doc #19166
Merged
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
edoakes
reviewed
Oct 6, 2021
| @@ -207,6 +207,46 @@ Please refer to the Kubernetes documentation for more information. | |||
| .. _`NodePort`: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types | |||
|
|
|||
|
|
|||
| Failure Recovery | |||
| ================ | |||
| Ray Serve is resilient to any component failures within the Ray cluster out of the box. | |||
There was a problem hiding this comment.
Can you please specify how process and worker node failures are handled?
doc/source/serve/deployment.rst
Outdated
| Failure Recovery | ||
| ================ | ||
| Ray Serve is resilient to any component failures within the Ray cluster out of the box. | ||
| However, when the Ray cluster goes down, you would need to recover the state by creating a new Ray cluster and re-deploys all Serve deployments into that cluster. |
There was a problem hiding this comment.
Specify that this mean the head node specifically
There was a problem hiding this comment.
And that Ray is not currently HA, but it's on the long term roadmap so this is a "temporary limitation"
doc/source/serve/deployment.rst
Outdated
Comment on lines
245
to
246
| While we have native support for on disk and AWS S3 storage, there is no reason we cannot support more. | ||
| You can easily try to plug into your own implementation using the ``custom://`` path and inherit the `KVStoreBase`_ class. |
There was a problem hiding this comment.
Add call to action to ask people to open a github issue and/or contribute a backend for this.
edoakes
added
the
@author-action-required
simon-mo
removed
the
@author-action-required
edoakes
approved these changes
Oct 21, 2021
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?
Port over the gist and highlight its experimental status.
Related issue number
Checks
scripts/format.shto lint the changes in this PR.