Is it advisable to add the Indexer Cluster Master as one of the Deployment Server clients?
Thanks in advance.
Hi morethanyell,
While this is technically possible, and I know some people actually have their cluster master configured to be a deployment client to be able to deploy configs to the cluster master and from there into the cluster, I would personally not recommend it.
The main reason for this is the simple fact that it is not supported by Splunk and once you have an issue, you most likely will be asked to fix that first 😉
Hope this helps ...
cheers, MuS
PS: better approach, use any other tool that can put config files in place like ansible, git, svc, placeAnyToolNameHere
and manage the config this way.
Hi morethanyell,
While this is technically possible, and I know some people actually have their cluster master configured to be a deployment client to be able to deploy configs to the cluster master and from there into the cluster, I would personally not recommend it.
The main reason for this is the simple fact that it is not supported by Splunk and once you have an issue, you most likely will be asked to fix that first 😉
Hope this helps ...
cheers, MuS
PS: better approach, use any other tool that can put config files in place like ansible, git, svc, placeAnyToolNameHere
and manage the config this way.
Is it sane to say that it will also add to the DS' burden in terms of network traffic and storage?
Yes, like any other deployment client that is phoning home every minute and polling for any configured app for them does.
cheers, MuS
Depends on the volume of your indexing. below is my environment with a small scale indexing (around 1GB/day)
Indexer Cluster - 2 servers
Seach head Cluster - 3 servers
DMC, CM, LM, DS, SHCD - 1 server
Not referring to having the DS and CM in one server. They're separate.