All Apps and Add-ons

Witch node (masterNode indexersNode searchHead) shoud be the licence manager in a clustered envirenment ?


I would like to add my Splunk Licence on a clustered envirenment, I have found no guidance in either the main Admin manual or the Indexing and Clustering manual on this...
Any help or guidance from someone who has done this would be appreciated !

0 Karma


The license master can be any splunk instance to which your cluster can connect, normally search head or master (splunk doesn't recommend to user indexer node). We used CM as license master(physical machine) before but now moved to a separate license master which is out of our cluster infrastructure as part of infra movement not because of performance issues.

As per , it's recommend to have a dedicated instance for deployment server and license master.

Architecture/ Deployment

Dedicated Deployment Server and license Master - If your install grows beyond just a single Splunk instance (talking indexers & search heads here, not forwarders), set up a separate server to be a license manager & Deployment server. A VM is fine for these purposes, and can actually be a benefit to be on a VM. You can even use the tarball install to put these multiple instances on the same box/VM. Say one in /opt/splunk, one in /opt/deploymentserver, and one in /opt/licenseserver. Run them on different ports of course.

If you are not planning for a dedicated instance for this, you can use a search head or CM as license master

What goes around comes around. If it helps, hit it with Karma 🙂
0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...