imbajin commented on code in PR #523: URL: https://github.com/apache/hugegraph-doc/pull/523#discussion_r4301522229
########## content/en/docs/config/config-backend-hstore.md: ########## @@ -246,3 +246,22 @@ curl http://localhost:8080/metrics/backend The `nodes` value in the response is the count of active stores PD returns. A `nodes` value of `0` means the Server reached PD but PD has no store in state `Up`, which usually means the Store nodes have not registered yet, or registered as `Pending` because they are not in PD's `pd.initial-store-list`. + +### 9 Legacy GraphID upgrade preflight + +HugeGraph-Store provides legacy GraphID upgrade preflight checks during bootstrap and upgrade processes. +Released 1.7.0 and earlier Store builds do not contain this preflight guard. +Use a Store build supporting this capability before relying on the refusal behavior below. + +These Store builds check existing graph-data column families before allocating a missing graph ID, first opening a cold +partition DB during metadata bootstrap, starting its Raft state machine, or activating a staged snapshot. Before pruning, the first cold DB open checks +all retained valid versions. Reserved `FFFE` legacy rows cause refusal. +An incomplete selected DB version without `CURRENT` is also rejected when it would hide retained valid versions. This concerns affected old write paths; +it does not mean that every 1.7 database needs migration, and the persisted ID format is unchanged. + +On refusal, preserve the original data DB versions, metadata, WAL and incoming/staged snapshots. Investigate the affected write and upgrade history before Review Comment: Updated both languages to explicitly state that released 1.7.0 and current master builds do not yet contain this preflight check (pending merge of the Store implementation), and pinned the documentation link to avoid 404. Once the code PR #3330 finalizes its refusal handling, we will document the exact observable Store state and logs accordingly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
