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 | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...