Repository navigation
docs: edge clusters: device-failure tolerance, journal RAID, relaxed migration - #239
Merged
Merged
Conversation
…migration A one-node edge cluster is not limited to 1+0: declared singleNode, it runs any supported scheme with one data device per chunk, and the parity protects against device failures. The journal on journal partitions is mirrored (RAID 1 / RAID 0+1) and survives any one device failure; two at once only within one striped group, so 1+2/2+2/4+2 on one node are guaranteed one failure at a time. A dedicated journal device (always used with Linux block devices) is not mirrored. Rebuild and rebalancing run in relaxed placement, so one- and two-node clusters need no extra node. Installation: singleNode declaration, discovery proposals for one and two workers, validation rules. Operations: failure table per scheme and journal placement, device failure on a two-node cluster, device addition, troubleshooting row. Hardware requirements box updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-edge-ec-tolerance |
…preferred node Follows simplyblock/simplyblock-operator#721: spec.clusterMode (Single, Dual, Standard) replaces singleNode and the twoNode declaration, enableArbitration and arbitration replace twoNode, and the preferred node is gone: a node without a grant fences itself at the end of the hold time. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
noctarius
approved these changes
Oct 13, 2026
Contributor
|
🤖: Deployment available as https://docstest.simplyblock.io/docs-edge-ec-tolerance |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to #236 (already merged). The edge pages said a one-node cluster runs 1+0 and loses the data of a failed device. That is a documentation error: the control plane activates a single-node cluster with any scheme, one chunk per device.
Single;clusterMode: Singledraft, theclusterMode: Dualdraft withenableArbitrationandarbitration, the discovery proposals for one and two workers, and the validation rules.Product changes this describes:
clusterMode(Single,Dual,Standard) replacessingleNodeand thetwoNodedeclaration,enableArbitrationandarbitrationreplacetwoNode, the preferred node is dropped, plus the scheme gates and the discovery proposals;relaxed_modefor migrations on 1- and 2-node clusters.The local quality gate is clean except
reference/api/index.md→openapi.json, a file CI generates.🤖 Generated with Claude Code