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!

How to Break a Kubernetes Pod on Purpose and Let the AI Troubleshooting Agent Find ...

Let's say I've just rolled out a Kubernetes Deployment with a typo in the image tag. Nothing explodes. The pod ...

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...

What's New in Splunk Enterprise Security 8.8 and Beyond

Threats move at machine speed. Keeping up should not depend on having the biggest budget, the largest team, or ...