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
Get Updates on the Splunk Community!

Stay Connected: Your Guide to January Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...

[Puzzles] Solve, Learn, Repeat: Reprocessing XML into Fixed-Length Events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...