Deployment Architecture

Can the same deployment server instance also act as the following: SH clustering deployer, As a Search Head in indexer cluster and Licence Master?

immortalraghava
Path Finder

Hello all,

I have a deployment server (license master) and an indexer cluster with 2 search heads. For now I have added deployment server also as a search head in the indexer cluster. I see no issues and the setup is fine.

Now with an additional search head I am planning to do SH clustering . So I think to use the deployment server (which is also a search head in indexer cluster) as SH deployer ?

Anyone has tried his before? Any help appreciated.

Thanks
Veera

1 Solution

FritzWittwer_ol
Contributor

Well you can certainly, but you probably don’t want, depends on the size of your infrastructure, you can run anything on one node, but for production environment’s you should not do it for various reasons
- Search head and deplyoer should be separate
- A deployment server which has to server more than 50 clients should act just as deployment server
- The deployer has to be a separate node

We run all this Splunk instances on one server for testing purposes, but in our planned production environment we will have 30 Indexers, 11 Search heads in two clusters, and then separate on virtual machines:
- the two deployer for both clusters
- a License server
- a few deployment servers, synchronized with rsync from a master
- a cluster master, made redundant with a linux cluster

View solution in original post

somesoni2
Revered Legend

The Splunk docs have good enough source for questions like this. See the SH Cluster deployment overview page to learn about different component and their requirements.

For requirement specifically for Deployer, see this http://docs.splunk.com/Documentation/Splunk/6.2.6/DistSearch/SHCsystemrequirements#Deployer_requirem...

FritzWittwer_ol
Contributor

Well you can certainly, but you probably don’t want, depends on the size of your infrastructure, you can run anything on one node, but for production environment’s you should not do it for various reasons
- Search head and deplyoer should be separate
- A deployment server which has to server more than 50 clients should act just as deployment server
- The deployer has to be a separate node

We run all this Splunk instances on one server for testing purposes, but in our planned production environment we will have 30 Indexers, 11 Search heads in two clusters, and then separate on virtual machines:
- the two deployer for both clusters
- a License server
- a few deployment servers, synchronized with rsync from a master
- a cluster master, made redundant with a linux cluster

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...