Deployment Architecture

Cluster -> master node and peer node on same machine

jtworzydlo
Path Finder

I have 4 machines (RHEL) and wanted to make 2 clusters (2 peer nodes per cluster) of these.
But one thing made me very sad.
"Important: The master cannot do double duty as a peer node or a search head, and it cannot reside on the same machine as a peer node or search head."

Is this really true? How would these instances know of each other if I change the install directory?
has anyone tried this approach?

Tags (1)

mahamed_splunk
Splunk Employee
Splunk Employee

The main reason we recommend to run each component of clustering (master, peer, search head) on separate server is because we don't want the failure of one component affects the other and bring down the entire cluster.

martin_mueller
SplunkTrust
SplunkTrust

Regardless of what may or may not be technically possible, putting more than one role of the cluster onto the same machine makes the system vulnerable to single points of failure. If for example a combined master/peer box goes down there is no master to redistribute the lost buckets.

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 ...