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#...

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...