Question 900
A scientific institute migrates standalone indexes into a cluster. Observed: The runbook copies arbitrary hot-bucket directories into live peer paths while indexing continues. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Historical queries reconcile and new peers report stable cluster bucket ownership) to the original warning (The runbook copies arbitrary hot-bucket directories into live peer paths while indexing continues). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
The proposed check applies to: Cluster peer-to-peer bucket copy transport requires permitted network reachability. The current failure was: The runbook copies arbitrary hot-bucket directories into live peer paths while indexing continues. Its validation must test: Historical queries reconcile and new peers report stable cluster bucket ownership.
This is an unrelated recovery test. It is connected to: Operations restart all indexers repeatedly, adding instability without addressing blocked repair capacity. The present source situation requires: Historical queries reconcile and new peers report stable cluster bucket ownership.
That gate watches a different case: Replication is complete but the configured search factor is not being met for some buckets. It does not detect the current warning: The runbook copies arbitrary hot-bucket directories into live peer paths while indexing continues. The necessary confirmation is: Historical queries reconcile and new peers report stable cluster bucket ownership.