Splunk Enterprise

Updating limits.conf spath field for index cluster

jerm1020rq
Explorer

I need to modify the limits.conf for an index cluster. My question is if i modify /$Splunk/etc/system/local/limits.conf can this be done on the cluster manager and pushed out or does this need to be modified on the individual indexers themselves?

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Correct.  etc/system/default has lowest priority, followed by apps, then etc/system/local.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Modifying $SPLUNK_HOME/etc/system/local on the CM has no effect on the indexers.  That's because the CM pushes apps to the indexers and apps cannot override etc/system/local.

To modify limits.conf, create a new app in the CM's master-apps directory, put limits.conf in the default directory, then push the bundle to the indexers.

---
If this reply helps you, Karma would be appreciated.

jerm1020rq
Explorer

Ah, so making an app with only the limits.conf and pushing it down to the indexers will take precedence over the limits.conf that already exists on the indexers under etc/system/default? Thank you for the response, I think if this is the case, I should be good to go. Thanks!

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Correct.  etc/system/default has lowest priority, followed by apps, then etc/system/local.

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...