Deployment Architecture

Distributed Search Heads

RKnoeppel
Engager

Problem replicating config (bundle) to search peer 'server:8089', timed out reading http reply.
I am getting the above error in my Distributed Search environment.

We have a load balanced address in front of 2 search heads with 2 indexers on the back end.

Tags (1)

RKnoeppel
Engager

I don't know how big the rep bundle is.

distsearch.conf file only has the following lines:

[distributedSearch]
servers = server1:port,server2:port

0 Karma

Damien_Dallimor
Ultra Champion

How big is your replication bundle ?

What are your settings in the replicationSettings stanza of you distsearch.conf file ?

FYI : there is also an option to mount bundles (using shared storage) rather than replication.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...