Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Re: repFactor is not set to auto docker-splunk ima...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
repFactor is not set to auto docker-splunk image
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?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
An upvote would be appreciated and Accept Solution if it helps!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's applies to traditional deployment of Splunk, I'm talking about splunk in docker.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Persistent Queue at TcpOut — One of Splunk's Most Practical Features
Catalog Is Now Generally Available on Splunk Cloud Platform
Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner
