bitflicker64 opened a new issue, #3212: URL: https://github.com/apache/hugegraph/issues/3212
## Feature Description (功能描述) The Server has no endpoint a Kubernetes readiness probe can use that reflects whether it can actually serve graph traffic. `/versions` (what the #3132 chart uses today) answers 200 as long as the REST layer is up, even when the cluster has no Store at all. Measured independently by @SebastianGruza on 2026-09-16 (apache/hugegraph#3132, comment of 19:31 CEST; scripts in SebastianGruza/hugegraph-validation, `docs/helm-chart-faults.md` scenario 7): with all Stores scaled to 0 on a running cluster, the Servers stayed `Running` and `ready=true` with 0 restarts for 150+ seconds, `/versions` answered 200 throughout, while every `GET /graph/vertices/<id>` ended in a 500 after the 30 s request bound (#3204). A Kubernetes Service therefore keeps routing traffic to Servers whose every real request fails. This is the Server-side twin of #3183, which was fixed for PD by #3185's unauthenticated `/v1/ready`. Proposal: an unauthenticated, cheap readiness endpoint on the Server (for example `/apis/readiness` or a flag on `/versions`) that returns 503 unless: 1. the Server's PD client currently has a usable PD connection, and 2. at least one Store is registered and Up from that Server's view (the graph list from PD plus one cheap Store call is the shape suggested in the #3132 thread). It must not require Basic auth: a Kubernetes `httpGet` probe cannot carry a credential without leaking it into the pod spec, which is exactly why #3185 made `/v1/ready` unauthenticated and why the auth interceptor already excludes `/actuator/**`, `/v1/health` and `/v1/ready` on PD. Chart side once this exists: `server.readinessPath` flips from `/versions` to the new path the same way `pd.readinessPath` moved to `/v1/ready`, and a Server with no working storage drops out of the Service instead of serving 500s. -- 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]
