topic Re: SHC cluster Label in Deployment Architecture

SHC cluster Label

locose — Mon, 07 Mar 2016 20:53:12 GMT

I’m trying to setup our Splunk DMC . I’m going through the setup instructions on the Splunk web site. I noticed 2 confusing instructions.

http://docs.splunk.com/Documentation/Splunk/6.3.3/DMC/Setclusterlabels
On this url, the instruction is to run splunk edit shcluster-config -shcluster_label on any of search head cluster member .

http://docs.splunk.com/Documentation/Splunk/6.3.3/DistSearch/SHCconfigurationoverview
On this url , the instruction is to run splunk edit shcluster-config -shcluster_label on each member of the search head cluster.

So should this command be executed on any of the search head cluster members or on each of the SHC members.

Thanks

Re: SHC cluster Label

ppeterson — Mon, 07 Mar 2016 21:53:56 GMT

I'm not sure if I understand the difference? If you are changing the label you need to change it on all of the search heads in the SHC in addition to having it consistent on the Deployer. A word of caution on 6.3.2, please ensure you have the config correct for the ./splunk init shcluster-config command - I had to re-configure the entire cluster to get this functioning properly. Additionally you will want to try to avoid using a "$" in the secret as when I got around to installing apps this appeared to cause issues in the CLI.

Re: SHC cluster Label

adauria_splunk — Mon, 07 Mar 2016 22:39:16 GMT

So that's the question - do it to a single member of the cluster, or do it to every member (plus the deployer, as you point out). You are saying you must do it to every member, but the doc shows it both ways. So if you're right, we need to change one of the docs.

Thanks!

Re: SHC cluster Label

hexx — Mon, 07 Mar 2016 23:02:59 GMT

The first document is correct: You should be able to set the search-head cluster label from any member instance. You set it once and it will be propagated to all members.

Note that this does not indeed include the deployer, for which you will need to set the label manually as it is not really a member of the cluster but rather a supporting instance for it.

I have amended the documentation to make this clear.