mirror of
https://github.com/pgsty/minio.git
synced 2026-09-06 18:46:17 +03:00
87c621965d
After a restart a node's remote erasure drives that could not be connected during startup stay uninstalled until the next connectDisks pass, about 15 seconds later. During that window the liveness, readiness and both cluster probes answer 200, admin info shows every drive online and mcli ready agrees, because the cluster probes aggregate each peer's report of its own local drives rather than the drives this node has installed. A PUT through that node can still fail with 503 SlowDownWrite and a cross-node GET can answer 404 NoSuchKey until the window closes. The behaviour is inherited from upstream and reproduced on the 0806 and 0903 releases alike. Document the window and the bounded data-path check (PUT through each node, read each object through every node, fixed deadline, re-read acknowledged objects) that automation should use instead of the probes, and correct the readiness probe description, which also fails on request-queue overload and an unreachable KMS. No product change: the probes keep their documented purpose, and changing them or the reconnect cadence was judged unproven tuning in the agreed plan. Refs pgsty/silo#116 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L7qJqWwy8oFA6aCXWRzXQe Signed-off-by: Feng Ruohang <rh@vonng.com>