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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...