Skip to content

docs(operations): correct storage recovery and deployment guidance - #571

Open
imbajin wants to merge 3 commits into
apache:masterfrom
hugegraph:docs/storage-deployment-refresh-20261115
Open

imbajin wants to merge 3 commits into
apache:masterfrom
hugegraph:docs/storage-deployment-refresh-20261115

Conversation

@imbajin

@imbajin imbajin commented Nov 16, 2026

Copy link
Copy Markdown
Member

Purpose of the PR

Give operators accurate storage and deployment guidance where old defaults or overly strong recovery statements could lead to the wrong action.

  • Separate PD bootstrap admission from runtime voter quorum, and clarify drain retries and startup lock handling.
  • Correct Raft segment defaults and explain Store recovery, deleted-graph metadata and learner promotion boundaries.
  • Replace long Server/Docker diagnostic paragraphs with log-location tables, explicit volume guidance and scoped JVM options.

Validation: source-contract and independent cross-review passed, along with strict artifact/link checks and desktop/mobile table-reader/Details checks. Existing routes, headings and version distinctions are retained.

Recovery and quorum statements were checked against source; the earlier minimal Helm run does not establish live HA or failure-recovery acceptance.

@bitflicker64 bitflicker64 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: no. Score: 9/10. Summary: The PD bootstrap and quorum rules, drain retry, 30-second metadata LOCK wait, 1 GiB raft.maxSegmentFileSize default, blank-segment isolation, Store recovery NOT_FOUND handling and learner catch-up text match StoreNodeService, ConfigService, HgKVStoreImpl, RaftSegmentLogStorage, PartitionManager and PartitionEngine on Server master; the Server and Docker diagnostics rewrite keeps the launcher behaviour of hugegraph-server.sh.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants