@srajarat2  thank you for your note. This helps! So, we could set the flag to false to override this behavior, correct? Also, it is not clear how much of the metadata is retained in the target peers after eviction(assuming this flag is set to true).  Could you share your thoughts.    Copy-paste from server.conf.spec (8.2.0) for future reference. evict_on_stable = <boolean> * When the source peer completes upload of a bucket to remote storage, it notifies the target peers so that they can evict any local copies of the bucket. * When set to true, each target peer evicts its local copy, if any, upon such notification. * When set to false, each target peer continues to store its local copy, if any, until its cache manager eventually evicts the bucket according to its cache eviction policy. * Default: false   ... View more

  According to this documentation:  https://docs.splunk.com/Documentation/Splunk/8.1.3/Indexer/SmartStorearchitecture "When the hot bucket rolls to warm, the data flow diverges, however. The source indexer copies the warm bucket to the remote object store, while leaving the existing copy in its cache, since searches tend to run across recently indexed data. The target indexers, however, delete their copies, because the remote store ensures high availability without the need to maintain multiple local copies.The master copy of the bucket now resides on the remote store."   Once the warm data buckets roll to remote storage,  target indexers delete their copies.     ... View more