Getting Data In

Indexes in an Index Cluster

dersa
Path Finder

Hi, we have an Indexer Cluster with a dedicated Cluster Manager. The indexers have an additional hard drive attached for the custom indexes. The cluster manager has only one hard disk.

When adding an Index to the cluster manager's indexes.conf  I am getting this error "Failed to create directory". Does it mean the cluster manager must have the same number of  hard disks as the indexers or would it be sufficient, to create an Variable (CUSTOM_INDEX) pointing on the cluster manager to /opt/splunk-home/var/lib/splunk and on the indexers it point to a folder on the additional hard disk?

thanks in advanced for sharing your wisdom

Alex

 

Labels (2)
0 Karma
1 Solution

PickleRick
SplunkTrust
SplunkTrust

You don't add indexes _to_ the CM. In fact CM should not be indexing anything locally. You want to forward all events from all your components to indexers. Indexers are the only components which should be doing local indexing. Other components should be only sending data "outwards" using outputs.conf and have local indexing disabled.

View solution in original post

dersa
Path Finder

Thanks Rick for your answer. I don't want to index anything on the CM. But I have to add the configuration on the CM in this file /opt/splunk/etc/manager-apps/_cluster/local/indexes.conf

I got an error message earlier, I think there were just some permissions missing. Everything looks good now. 

Thanks a lot for your quick feedback

Alex

0 Karma

PickleRick
SplunkTrust
SplunkTrust

OK. The $SPLUNK_HOME/etc/manager-apps directory contains only apps which are pushed to indexers. They are not applied locally. So your problem must have been (and was as you found yourself) caused by something else.

0 Karma

PickleRick
SplunkTrust
SplunkTrust

You don't add indexes _to_ the CM. In fact CM should not be indexing anything locally. You want to forward all events from all your components to indexers. Indexers are the only components which should be doing local indexing. Other components should be only sending data "outwards" using outputs.conf and have local indexing disabled.

Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...