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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...