Deployment Architecture
Highlighted

Multisite Indexer Clustering

Path Finder

I am looking at possible setting up multisite indexer clustering on some new indexers we are setting up. We have 2 indexers each in 2 sites.

If I wanted 1 copy of data to stay in the site and a replicated copy to be in the other site, would I just need to set the site replication value to this:

availablesites=site1,site2
site
replication_factor = origin:1,total:2

From reading the document on multisite indexer clustering, I see this line and assume that the above setting would force 1 copy on the originating site and since the other site does not have a copy it would push the required replicated copy to that site.

Because the total value can be greater than the total set of explicit values, the cluster needs a strategy to handle any "remainder" bucket copies. Here is the strategy:
If copies remain to be assigned after all site and origin values have been satisfied, those remainder copies are distributed across all sites, with preference given to sites with less or no copies, so that the distribution is as even as possible. Assuming that there are enough remainder copies available, each site will have at least one copy of the bucket.

Is my assumption correct?

0 Karma
Highlighted

Re: Multisite Indexer Clustering

SplunkTrust
SplunkTrust

That is correct. With origin (say site1) is fullfilled, there will be one remainder copy left which will be assigned to site2 as it has no copies of that data bucket. This is much simpler as there are only two sites involved.

View solution in original post

Highlighted

Re: Multisite Indexer Clustering

Path Finder

Thanks for the confirmation!

0 Karma
Highlighted

Re: Multisite Indexer Clustering

Motivator

Hey jeffbat,

Yes you are correct.
availablesites=site1,site2
site
replication_factor = origin:1,total:2
This setting will keep replication across sites and primary copy at which the data is indexed.

All the best with your setup!!

0 Karma