I'm not fully understanding the documentation around the delta replication from a deployer to the search heads(or cluster). Is it correct in saying that when the bundles are being copied from the deployer to the captain, that only "changes" are being created in the bundle and that is where the .delta files come in? Those .deltas are then replicated out to the cluster members? Apologize if the question is not clear. I really just want to completely understand the process outlined here
http://docs.splunk.com/Documentation/Splunk/7.1.3/DistSearch/PropagateSHCconfigurationchanges
How the cluster applies the configuration bundle
if there is any modification in any file in particular app then whole app tar is created ..the whole app is get replaced and not the only file that has been changed and previous app will be available in default.old.<date>
folder
yes..
So first deployer stags the configuration bundle in a separate location on it's file system- $SPLUNK_HOME/var/run/splunk/deploy
and then pushes the app directories to each cluster member...and then each cluster member applies app tarball locally . yes that's deployment of app.
thank you, that is good to know. Once the bundle is replicated to the members, it's deployed(un-tarred) into the app(s) directory correct? that's basically the deployment correct?