Is there a way to setup a multi-site Search Head cluster to prevent replication of KV and CSV to other sites?

[Sivrat]

I currently have an Indexer/Multiple Search Head cluster, but due to some regional requirements we are looking at smaller replicas of the environment in other regions.

We need to have certain configurations, such as saved searches and dashboards, copied over to the new regions. However, we need some stuff, like the contents of lookup files, to not replicate over.

Is there a way to setup a multi-site Search Head cluster to prevent replication of KV and CSV to other sites, but allow replication within each site? Or prevent single search heads in a cluster from receiving updates to their lookups? I know there are ways to prevent copies of indexed data from leaving a site, but not sure on bundle replication objects how exactly it processes.

[somesoni2]

Splunk search head cluster members are not site aware so you can't setup replication restriction for a specific site (it'll apply for all members in all site). Read more here.

https://docs.splunk.com/Documentation/Splunk/8.2.6/DistSearch/DeploymultisiteSHC#Search_head_cluster...

[richgalloway · Accepted solution]

Search head clusters do not have a concept of site.  The SHC can span multiple locations, but it's all considered one "site".  Except for the captain, all members nodes are treated as equals.

Consider making a case for multi-site SHC at https://ideas.splunk.com