[31/N][VirtualCluster] add virtual cluster documents #470
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
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
| **Raylet Failover** | ||
| When Rayle dies or restarts, the GCS Server will detect that the node is dead and then update the status of the corresponding node in the virtual cluster, and the virtual cluster manager will periodically check for dead nodes and replace them with new ones. | ||
|
|
||
| There are 4 scenario that the virtual cluster manager will replenish new nodes for the virtual cluster, and the state of the virtual cluster need flush or publish: |
There was a problem hiding this comment.
There are four scenarios in which the virtual cluster manager will replenish new nodes for the virtual cluster, and the state of the virtual cluster needs to be flushed or published:
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
| 1. Select new alive undivided node with the same node type as the dead one from :math:`V_{primary}` to replace the dead one. | ||
| 2. If there are still dead nodes inside :math:`V_{job}`, then continue to new alive undivided node with the same node type as the dead one from it's parent virtual cluster nodes :math:`V_{divisible}` to replace the dead one. | ||
| 3. If there are any dead node inside :math:`V_{job}` is replenished, then flush the :math:`V_{job}` to the storage and publish it to all the worker nodes. | ||
| 4. If there are any dead node inside :math:`V_{divisible}` (parent virtual cluster of :math:`V_{job}`) is replenished, then just flush the :math:`V_{divisible}`, without publish. |
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
wumuzi520
force-pushed
the
dev-hc
branch
4 times, most recently
from
934daa2 to
5a67f24
Compare
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
doc/source/virtual-cluster/cli.rst
Outdated
|
|
||
| **Output:** | ||
|
|
||
| `Virtual cluster 'myCluster' created successfully` |
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
xsuler
reviewed
Jan 20, 2025
Signed-off-by: 黑驰 <[email protected]>
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?
This PR is 31/N implementation of the VirtualCluster (see issue #409), Add virtual cluster documents.
Related issue number
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.