Question 440
A design authority reviews this scenario: Indexer disk exhaustion prevents bucket fix-up even though peer network links are healthy. Which underlying mechanism explains it?
Explanation
Correct Answer
Cluster repair requires resources for additional copies, so restoring connectivity alone does not establish completeness. This technical distinction is illustrated by: Indexer disk exhaustion prevents bucket fix-up even though peer network links are healthy. The recommended operational decision is: Check disk headroom and writable storage on every eligible recovery peer before triggering repair. Evidence should show: Replication backlog clears after sufficient storage is provided and copy-count targets are achieved.
Incorrect Answers
The competing mechanism can matter elsewhere, for instance: An indexer cluster's peers do not agree on the shared cluster secret and one member stays disconnected. The target problem instead rests on cluster repair requires resources for additional copies, so restoring connectivity alone does not establish completeness.
Consider the alternative example: A site disaster removes a subset of origin copies and repair cannot reestablish the required total after failover. In that example, multisite placement reduces risk only for the failure scopes and control-plane dependencies actually protected by the design. The present question requires the different technical explanation that cluster repair requires resources for additional copies, so restoring connectivity alone does not establish completeness.
Consider the alternative example: An operator disables a peer before checking that another peer is already in a recovery state. In that example, availability depends on the number of remaining searchable copies and their placement, which simultaneous outages can violate. The present question requires the different technical explanation that cluster repair requires resources for additional copies, so restoring connectivity alone does not establish completeness.