Deployment Architecture

how to manually control app config reload of specific deployment client



I have several critical UF/HF that providing equivalent service in a load-balanced topology.
I would like to leverage deployment server / client feature to push the configuration to them, but would like to control when a given DS client will really download/apply the config.
For example, I have 3 nodes acting as load-balanced HTTP Event Collector. I would like to trigger the update through DS of one node, wait the node to apply the change, before proceeding with others.

Questions :
- is it possible to disable automatic config update of a given instance (Splunk Enterprise or UF)
- then is there a command that can be run locally or remotely to trigger the usual DS client refresh on-demand/manually


0 Karma
Get Updates on the Splunk Community!

Splunk Lantern | Getting Started with Edge Processor, Machine Learning Toolkit ...

Splunk Lantern is Splunk’s customer success center that provides advice from Splunk experts on valuable data ...

Enterprise Security Content Update (ESCU) | New Releases

In the last month, the Splunk Threat Research Team (STRT) has had 2 releases of new security content via the ...

Announcing the 1st Round Champion’s Tribute Winners of the Great Resilience Quest

We are happy to announce the 20 lucky questers who are selected to be the first round of Champion's Tribute ...