https://community.splunk.com/t5/Deployment-Architecture/Is-the-deployer-part-of-the-search-head-cluster/m-p/170958#M6398 <P>No. You just point the members of the cluster to the deployer. Reference our docs here: <A href="http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/SHCdeploymentoverview">http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/SHCdeploymentoverview</A></P> <P>You don't even need to point the cluster members to a deployer for it to function. But, the only supported method to deploy apps to the cluster is by the use of the deployer. </P> <P>You are probably getting a little tripped up in how the deployer knows it's a deployer. In 6.2 any instance can be a deployer. Mothership splunkd is always "listening" for comms from a search head cluster. And when you first bootstrap a cluster, if you point it to a instance you have decided to be the deployer, then the cluster members communicate with it to make sure it is available. </P> Mon, 09 Mar 2015 14:06:50 GMT RicoSuave 2015-03-09T14:06:50Z https://community.splunk.com/t5/Deployment-Architecture/Is-the-deployer-part-of-the-search-head-cluster/m-p/170957#M6397 <P>Hi,</P> <P>In SHC, is the Deployer considered part of the cluster? Should I run the "init schcluster-config" commands on that specific server? </P> Mon, 09 Mar 2015 13:43:24 GMT https://community.splunk.com/t5/Deployment-Architecture/Is-the-deployer-part-of-the-search-head-cluster/m-p/170957#M6397 a212830 2015-03-09T13:43:24Z https://community.splunk.com/t5/Deployment-Architecture/Is-the-deployer-part-of-the-search-head-cluster/m-p/170958#M6398 <P>No. You just point the members of the cluster to the deployer. Reference our docs here: <A href="http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/SHCdeploymentoverview">http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/SHCdeploymentoverview</A></P> <P>You don't even need to point the cluster members to a deployer for it to function. But, the only supported method to deploy apps to the cluster is by the use of the deployer. </P> <P>You are probably getting a little tripped up in how the deployer knows it's a deployer. In 6.2 any instance can be a deployer. Mothership splunkd is always "listening" for comms from a search head cluster. And when you first bootstrap a cluster, if you point it to a instance you have decided to be the deployer, then the cluster members communicate with it to make sure it is available. </P> Mon, 09 Mar 2015 14:06:50 GMT https://community.splunk.com/t5/Deployment-Architecture/Is-the-deployer-part-of-the-search-head-cluster/m-p/170958#M6398 RicoSuave 2015-03-09T14:06:50Z https://community.splunk.com/t5/Deployment-Architecture/Is-the-deployer-part-of-the-search-head-cluster/m-p/170959#M6399 <P>Do not run "init shcluster-config" on the deployer. You only run that command on instances that you are enabling as cluster members, and a cluster member cannot be a deployer. </P> <P>See <A href="http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/SHCsystemrequirements#Deployer_requirements">http://docs.splunk.com/Documentation/Splunk/6.2.2/DistSearch/SHCsystemrequirements#Deployer_requirements</A></P> Mon, 09 Mar 2015 16:51:53 GMT https://community.splunk.com/t5/Deployment-Architecture/Is-the-deployer-part-of-the-search-head-cluster/m-p/170959#M6399 Steve_G_ 2015-03-09T16:51:53Z