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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...