Question 810
A Splunk platform team observes this behavior: While evaluating a cloud migration program in a verification workshop, operations report: A new indexer is healthy but the search head cannot query it because the trusted peer relationship was never established. Which technical principle best explains the issue?
Explanation
Correct Answer
The controlling mechanism is that A healthy standalone indexer is not automatically an active peer for every search head. Resolve the problem by add or repair the appropriate search-peer configuration and verify network and authentication trust. Then validate with: The peers list includes the new node and a distributed search returns its indexed events.
Incorrect Answers
This principle explains a different operational condition: A troubleshooting note says the search head stores the primary raw index buckets and indexers only provide authentication. For the current issue, A healthy standalone indexer is not automatically an active peer for every search head. The corresponding action is Add or repair the appropriate search-peer configuration and verify network and authentication trust.
The option would apply to “A query succeeds on one indexer but fails from the search head after a new peer is added”. The controlling mechanism is that search dispatch requires a functioning search-head-to-peer relationship, not just data on disk. This question instead requires “A healthy standalone indexer is not automatically an active peer for every search head”.
The related but distinct situation is “A search job finishes slowly and an operator immediately adds more indexing storage without checking peer search load”. Query coordination bottlenecks and peer-side execution bottlenecks require different remedies. For the stated problem, “A healthy standalone indexer is not automatically an active peer for every search head” addresses the central condition.