[SmartStore]Role of file .buckets_synced_to_remote_storage in migration from local to SmartStore.

[rbal_splunk]

Lets assume that I have 20 node Indexer cluster deployments. Enabled smart store and migration started but due to a network issue the migration was interrupted. We are trying to figure out the best way to restart a migration. How can that be done? What is role of file .buckets_synced_to_remote_storage in migration?

[rbal_splunk · Accepted solution]

Please contact Splunk Support on detailed process.
Never touch .buckets_synced_to_remote_storage

[mdoyle_splunk]

Do NOT remove this file unless you also change the indexer GUID using splunk clone-prep-clear-config or it will possible corrupt previously uploaded buckets that have been evicted from the local cache.

clone-prep-clear-config is safe to use because it emulates a new indexer being added to the cluster and it will not upload buckets that already exist that were uploaded by a different indexer.

If there is any possibility that your data on the indexer is not 100% complete due to eviction, you MUST change the guid when removing .buckets_synced_to_remote_storage