Deployment Architecture

Delayed results when running a search from a search head cluster, with message about not being able to establish a common bundle version.

Steve_G_
Splunk Employee
Splunk Employee

When I run a search on a search head cluster member, the results are delayed and I get the message, "“Gave up waiting for the captain to establish a common bundle version across all search peers; using most recent bundles on all peers instead."

What's the problem?

Tags (1)
1 Solution

Steve_G_
Splunk Employee
Splunk Employee

The usual cause for this error is a misconfiguration of search peers on one or more cluster members. All members must use the exact same set of search peers.

See: http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/Connectclustersearchheadstosearchpeers#...

View solution in original post

Steve_G_
Splunk Employee
Splunk Employee

The usual cause for this error is a misconfiguration of search peers on one or more cluster members. All members must use the exact same set of search peers.

See: http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/Connectclustersearchheadstosearchpeers#...

Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...