docs: add single-region DR solution to disaster recovery overview - #2803
Closed
fengjiachun wants to merge 1 commit into
Closed
docs: add single-region DR solution to disaster recovery overview#2803fengjiachun wants to merge 1 commit into
fengjiachun wants to merge 1 commit 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.
Deploying greptime-docs with
|
| Latest commit: |
7c3365a
|
| Status: | ⚡️ Build in progress... |
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.
What changed
The disaster recovery overview jumped from GreptimeDB Standalone straight to the cross-region topologies. Missing was 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.
This adds that section to the overview in both locales, plus a matching row in the solution comparison table.
How it is written
The section follows the shape of DR Solution Based on Cross-Region Deployment in a Single Cluster, so the two read as one family:
Latencies:andSupports High Availability:lists.Facts are taken from the existing pages on Region Failover, WAL and metadata management. The latency list does not repeat the example millisecond values from the cross-region page, since there are no measured single-region numbers to quote.
Diagram
New
static/Single-region-single-cluster.svg, drawn in the same style asstatic/img/active-active-forwarding.svg(Arial,#6f6fff,title/descfor accessibility) and shared by both locales like the other DR images.Scope
Nightly only:
docs/and the Chinesecurrent/tree. Backporting to v1.2 can follow separately.Checks
DOC_LANG=en pnpm check:linkspassesDOC_LANG=zh pnpm check:linkspasses, including the new image path and the Chinese anchorsgit diff --checkclean; no lockfile or generated files touched