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!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...