Deployment Architecture

Help on Splunk deployment plan

jg91
Path Finder

Hello friends,
We want to deploy splunk in a new site and we have 2 powerful server with SSD storage, We need to have data high availability and our current plan is to install one indexer on each server and use 1 Heavy Forwarder on 3rd server to send data to both indexers.
Is this plan good enough or there is a better plan like using indexer clustering and install cluster master on 3rd server?
Please share your suggestions with me about deployment architecture with 2 server.
Thanks,

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Use an indexer cluster to replicate your data.

Forcing a HF to send data to two indexers creates more problems than it solves. Your license will be hit twice. Your searches will return duplicate results. Any failure to connect to indexer (like during maintenance) means your data is no longer in two places. Clustering resolves all of these issues.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Use an indexer cluster to replicate your data.

Forcing a HF to send data to two indexers creates more problems than it solves. Your license will be hit twice. Your searches will return duplicate results. Any failure to connect to indexer (like during maintenance) means your data is no longer in two places. Clustering resolves all of these issues.

---
If this reply helps you, Karma would be appreciated.

jg91
Path Finder

Thank you, I used your solution.

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...