SebastianGruza commented on issue #3212: URL: https://github.com/apache/hugegraph/issues/3212#issuecomment-5735686237
PR is up: #3221. The design held, with two corrections the k3s runs forced (both kept as evidence in the validation repo): 1. The first probe pinged each Store with the store client's `existsTable` (a raft-routed call over the shared session pool). It flapped on a rolling restart of the Stores and of PD (200→503→200 several times per Server) because a healthy node's ping waited behind a leaving one. Replaced by a direct, local, read-only `HgStoreState.getScanState` per node over the probe's own channels, fired in parallel, first answer wins. 2. Probing PD on every request made readiness track PD, not storage: PD→0 turned Servers NotReady while the data plane served fine. PD is now refreshed in the background and the last known Store list is used immediately; PD down/slow/restarting only flips `pd_reachable`. Final E2E on a 3-node k3s with the #3218 chart, 1 Hz sampling of /readiness, /versions, the Ready condition and the Service endpoints per Server pod, load through the Service: 7 PASS. Stores→0 pulls every Server out of the Service in ~30 s and back ~20 s after they return; rolling restart of Stores and of PD show zero readiness transitions; PD→0 stays 200 with pd_reachable=false; SIGSTOP on the busiest Store shows zero transitions. Scripts, per-scenario JSON and the two superseded designs: https://github.com/SebastianGruza/hugegraph-validation/tree/master/results/issue-3212 Chart side (`server.readinessPath`, default /versions, mirroring pd.readinessPath) is ready as a diff for hugegraph/hugegraph#221. -- 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]
