Repository navigation
Conversation
- describe startup source recovery and failure retries - document local deletion protection across graph spaces - explain authentication and cache RPC reload limits
- align configuration references with startup sources - preserve reload protection and recovery boundaries - wrap the added prose to the repository line limit
- document overlapping reload rejection and retry - qualify closed graph cleanup and data boundaries - explain local task owner waits and forced cancellation
- merge current documentation master - align schema graph space routes with the Go client - preserve merged edge label and error guidance
imbajin
changed the title
- describe the manager lifecycle admission guard - retain explicit retry and notification boundaries - align the Chinese and English API guidance
- explain deferred remote graph removal notifications - include overlapping operations in reload error summary - distinguish local waiting from distributed task deletion
- require quiesced writes during deletion and retries - retain failed owners only for cleanup recovery - explain partial deletion and closed task admission
- describe local publication and notification coordination - retain quota and local configuration protection rules - prohibit same-name recreation during failed cleanup - document explicit recovery after replacement failures
- describe waiting behind an active lifecycle operation - state the wait has no configured timeout - distinguish interruption and immediate API rejection
- make file removal mandatory for reload and restart - explain retained files restore deletion protection - preserve the DEFAULT graph-space protection scope
imbajin
marked this pull request as draft
October 12, 2026 17:04
- describe local task drain and manual maintenance - require restart for configuration changes - clarify uncertain cleanup and reload data risk - preserve existing Go schema routing guidance
imbajin
changed the title
This branch has not been deployed
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.
Graph maintenance documentation described guarantees beyond the current Server behavior. Align the Chinese and English API, configuration, FAQ and quickstart pages with the local task-drain and graph-deletion scope of apache/hugegraph#3308.
Stop writes and tasks on every participating Server before maintenance. Confirm deletion and cleanup on each Server before recreating the same name; notifications do not form a cluster barrier. Use restart for configuration changes, and inspect uncertain cleanup. Reload retains its existing backend-clear risk without PD; the pages do not promise global recovery or replacement ownership.
Keep the existing Go GraphSpace schema-routing correction and API parameters. Complete private-space CRUD and multi-Server acceptance remain open.
Validation: existing source tests, links, strict Hugo builds, versioned artifacts, search checks and bilingual rendered-page readback passed; one independent final documentation review found no outstanding issue. Both PRs remain drafts while current-head CI and the matching Server integration are tracked.
Org validation: hugegraph#45