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.
- 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