Hi Guys,
Can anyone here help me out for a steps and configuration required to make an instance as only Deployer.
I gone through the below links, but it will be kind assiastance if anyone simplify it better.
https://answers.splunk.com/answers/268768/deployment-server-vs-deployer.html
http://docs.splunk.com/Documentation/Splunk/6.2.3/DistSearch/PropagateSHCconfigurationchanges
If you still are on 6.2.3 as indicated by the docs links, do upgrade to 6.5.2 - there have been many SHC improvements over the years.
The docs likely have improved as well, here's the current detailed list of what to do to set up your SHC - including deployer: http://docs.splunk.com/Documentation/Splunk/6.5.2/DistSearch/SHCdeploymentoverview#Deploy_the_cluste...
If you're following that and still have questions, let us know what part doesn't work out for you.
If you still are on 6.2.3 as indicated by the docs links, do upgrade to 6.5.2 - there have been many SHC improvements over the years.
The docs likely have improved as well, here's the current detailed list of what to do to set up your SHC - including deployer: http://docs.splunk.com/Documentation/Splunk/6.5.2/DistSearch/SHCdeploymentoverview#Deploy_the_cluste...
If you're following that and still have questions, let us know what part doesn't work out for you.
That's intentional, many settings should not be performed on one cluster member only. These should be deployed through the deployer to keep all cluster members in sync.
To avoid breaking things, only settings that are safe to set through the UI are exposed by default.
Relevant docs: http://docs.splunk.com/Documentation/Splunk/6.5.2/DistSearch/HowconfigurationworksinSHC
I highly recommend following the steps from the documentation, including running the init shcluster-config on every instance (necessary to tell the instance "you're now part of a cluster") and bootstrapping the captain (necessary to tell the cluster "go!").
Pushing step 1 from the deployer is not going to work, because step 1 is where the cluster members learn about the deployer.
Pushing step 2 from the deployer is not going to work, because it pushes apps to all members. Assigning a bootstrap captain is an operation you do on only one instance.
One last understanding from you, hope you will help me out.
When I start making search head instance into cluster mood, why most of the options vanish from settings.
How can I keep all the options available intact after search head cluster inside setting.
Hi martin_mueller,
Thanks for sharing the link. Based on that details, I configured the Deployer only up-to shclustering stanza.
[shclustering]
shcluster_label = new_cluster1
pass4SymmKey = $1$vZu7quK4ZPxUzEb7xd/1
Now my question are below: