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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...