pallavithegod commented on code in PR #532:
URL: https://github.com/apache/hugegraph-doc/pull/532#discussion_r4306805403


##########
content/en/docs/quickstart/hugegraph/hugegraph-helm-operations.md:
##########
@@ -31,10 +31,18 @@ Store wait and Helm test reuse existing component images 
with `curl` already ins
 
 PD listens on REST 8620, gRPC 8686 and Raft 8610; Store on REST 8520, gRPC 
8500 and Raft 8510; Server HTTP on 8080; Hubble HTTP on 8088.
 Client Services hide individual Pod addresses. NodePort is a separate 
allocated port on reachable nodes, not the application listener port.
-PD `/v1/ready` requires a Raft leader; `/v1/health` only confirms the 
listener. Store startup waits for a majority of ready PD peers.
+PD `/v1/ready` requires a Raft leader. On older images, `/v1/health` only 
confirms the listener.
+Store startup waits for a majority of ready PD peers.
 Server waits up to `server.storageWaitTimeoutSeconds` (default 300) before its 
application startup; adjust it for slow storage bootstrap.
 No local Helm rendering verifies live cluster reachability, volumes or JVM 
capacity.
 
+Images containing the [fatal PD health 
fix](https://github.com/apache/hugegraph/pull/3358) return `503` from 
`/v1/health`
+after a terminal Raft error or shutdown; ordinary elections and quorum loss 
remain live (`200`).

Review Comment:
   Rechecked against e78588131, which preserves terminal state across queued 
callbacks and passes the full PD core profile. The paragraph remains 
conditional on images containing that fix, and the linked code/documentation 
merges need coordination.



-- 
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]

Reply via email to