Deployment Architecture

How do we add existing indexes into a new indexer cluster?

brdr
Contributor

Hi,

We are using Splunk Enterprise 6.4.

We recently brought up an indexer cluster with 2 indexers. The primary indexer is an existing indexer with about 15 indexes. The other indexer is brand new. When I established the cluster, as expected, the _audit, _internal, and main indexes started replication.

I now need to add existing indexes into the cluster. How do I do this? As an example, we have an existing index called 'network'. This index attributes are contained in etc/apps/laucher/local/indexes.conf. Would I update the indexers.conf (etc/master-apps/_cluster/local) on the cluster master this way?:

[network]
repFactor = auto

Do I need to push this as a config bundle?

I realize these indexes have older data that we do not need replicated, however, going forward, we expect the events for these existing indexes will be replicated with new data.

Thank you

0 Karma

Steve_G_
Splunk Employee
Splunk Employee

All the peer nodes in the cluster should use the same indexes.conf. You distribute it to the peers via the configuration bundle method. See: http://docs.splunk.com/Documentation/Splunk/6.4.1/Indexer/Configurethepeerindexes

Also, as you note, you cannot migrate the standalone buckets created pre-cluster, but they will remain searchable. See: http://docs.splunk.com/Documentation/Splunk/6.4.1/Indexer/Migratenon-clusteredindexerstoaclustereden...

Get Updates on the Splunk Community!

What the End of Support for Splunk Add-on Builder Means for You

Hello Splunk Community! We want to share an important update regarding the future of the Splunk Add-on Builder ...

Solve, Learn, Repeat: New Puzzle Channel Now Live

Welcome to the Splunk Puzzle PlaygroundIf you are anything like me, you love to solve problems, and what ...

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...