Getting Data In

repFactor is not set to auto docker-splunk image

davidgreenibm
New Member

Hi all,
I'm working on deploying index clustering in kuberntes using docker-splunk image and faced with the following issue:
By default on indexers when you configure cluster indexing repFactor is set to 0 what prevent replication between indexers. Should this be fixed in the nearest time or better to fix by your own?
I'm interested,how people who faced with it resolved this issue?

0 Karma

codebuilder
Influencer

You are correct. The default value for repFactor is zero, which means no replication.
If you omit the parameter from indexes.conf, that is the value you get, and no replication.
You need to explicitly set the value at either the global, or per index level within indexes.conf to override the default.

https://docs.splunk.com/Documentation/Splunk/8.0.2/Indexer/Configurethepeerindexes#The_indexes.conf_...

----
An upvote would be appreciated and Accept Solution if it helps!
0 Karma

manjunathmeti
Champion

Attribute repFactor is set during index configuration. By default it is set to 0. You need to change it to auto when you create an index.

0 Karma

davidgreenibm
New Member

It's applies to traditional deployment of Splunk, I'm talking about splunk in docker.

0 Karma

davidgreenibm
New Member

You can't set this param in UI and setting this param on every indexer sounds odd,especially when there is an ansible role that should configure all indexers as a cluster.

0 Karma
Get Updates on the Splunk Community!

Application management with Targeted Application Install for Victoria Experience

  Experience a new era of flexibility in managing your Splunk Cloud Platform apps! With Targeted Application ...

Index This | What goes up and never comes down?

January 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Splunkers, Pack Your Bags: Why Cisco Live EMEA is Your Next Big Destination

The Power of Two: Splunk + Cisco at "Ludicrous Scale"   You know Splunk. You know Cisco. But have you seen ...