Getting Data In

What are best practices on setting the replication factor for X number of indexers in an indexer cluster?

dhavamanis
Builder

Need your help,

We are trying to increase the number of indexer nodes in the indexer cluster for max availability approach. Can you please share the best Splunk replication factor vs number of indexer nodes? Because we want to use minimal storage and all time data availability for search even if one or two nodes went down in the indexer pool.

0 Karma
1 Solution

somesoni2
Revered Legend

IMK, the Replication factor is set uses only criteria which depends on "How many node failure you can tolerate without data loss".
So,

Replication Factor = No of allowed Indexer failure +1 

If you've 4 indexers and want all data to available even with 2 nodes failed then you need replication factor of 3 and so on.

See this for more information

http://docs.splunk.com/Documentation/Splunk/6.4.1/Indexer/Thereplicationfactor#Replication_factor_an...

View solution in original post

somesoni2
Revered Legend

IMK, the Replication factor is set uses only criteria which depends on "How many node failure you can tolerate without data loss".
So,

Replication Factor = No of allowed Indexer failure +1 

If you've 4 indexers and want all data to available even with 2 nodes failed then you need replication factor of 3 and so on.

See this for more information

http://docs.splunk.com/Documentation/Splunk/6.4.1/Indexer/Thereplicationfactor#Replication_factor_an...

Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...