docs: add single-region DR solution to disaster recovery overview - #2804
Open
fengjiachun wants to merge 2 commits into
Open
docs: add single-region DR solution to disaster recovery overview#2804fengjiachun wants to merge 2 commits into
fengjiachun wants to merge 2 commits into
Conversation
The disaster recovery overview jumped from GreptimeDB Standalone straight to the cross-region topologies, leaving out the tier most production clusters actually run: a single cluster inside one region, tolerating the loss of a node or of a single AZ through Region Failover. Add that section to the overview in both locales, following the shape of the cross-region page (AZ definition, Latencies, Supports High Availability), and add a matching row to the solution comparison table. The section states the conditions the RPO and RTO targets depend on: Region Failover is disabled by default, the surviving Datanodes need spare capacity, and the recovery time is dominated by WAL replay. Add Single-region-single-cluster.svg for the section, drawn in the same style as the existing hand-authored SVG diagrams.
The Datanode in AZ B was drawn with a line into the metadata backend, which it never talks to. Route both Datanodes onto a shared bus that feeds only the remote WAL and the object storage, and give Metasrv its own link to the metadata backend.
Deploying greptime-docs with
|
| Latest commit: |
e983a7b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3ca2e1b3.greptime-docs.pages.dev |
| Branch Preview URL: | https://docs-single-region-dr-soluti.greptime-docs.pages.dev |
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
1 participant
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.
Adds the tier missing between Standalone and the cross-region topologies: a single cluster in one region, surviving the loss of a node or of a single AZ through Region Failover.
Written to match the cross-region page — same AZ definition (a data center, or a compartment of one), same
Latencies:andSupports High Availability:lists — plus a row in the comparison table and a new diagram. Both locales, Nightly only.The latency list carries no millisecond values: the ones on the cross-region page are labelled examples, and there are no measured single-region numbers to quote.
DOC_LANG=enandDOC_LANG=zhpnpm check:linksboth pass.