SebastianGruza commented on issue #3203: URL: https://github.com/apache/hugegraph/issues/3203#issuecomment-5705061592
Server-side fix in #3210: with `usePD=true`, `GraphManager` waits for `pd.initial-store-count` active stores in PD before it opens the first hstore graph, bounded by a new option `pd.stores_wait_timeout` (default 300 s, 0 restores today's behaviour). Measured on the same reproduction as above (1 PD + 3 Store + 1 Server from a tarball, stores registering +5 s and +71 s after PD, `usePD=true`, first boot): | server | result | |---|---| | master `1a15e762` | 18 × `error code = 105`, backoff 1,1,1,2,3,4,5,6,7,8, `upper limit : 10`, **exit 1 after 38 s** | | `1a15e762` + #3210 | `PD needs 3 active store(s) … waiting up to 300s`, 14 progress lines (`0/3 → 1/3 → 3/3`), `3 active store(s) in PD after 70s`, **0 × 105, exit 0 after 81 s**, REST 200 | | + #3210, `pd.stores_wait_timeout=20`, stores at +120 s | 5 progress lines, then `Timed out after 20s waiting for 3 active store(s) in PD (0 registered); start the stores first or raise pd.stores_wait_timeout`, exit 1 after 31 s | Two things from the measurement. The wait has to sit before any graph is opened, not only before the system graph is created: with a local `conf/graphs` hstore graph, that local graph is the first to hit the 10-retry ceiling. And `getPDConfig()` does not send `min_store_count` (`ConfigService` builds the response from `partition_count` and `shard_count` only), so the server takes `shard_count`; on a cluster where `pd.initial-store-count` differs from the replica count PD should fill that field, a one-line follow-up on the PD side. Logs and script: `results/issue-3203/fix/` in https://github.com/SebastianGruza/hugegraph-validation. The `[wait-storage]` gate from #3132 stays the right thing for images; this change covers the tarball and any start without an orchestrator. -- 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]
