<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How does Splunk check for server ulimit values? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-check-for-server-ulimit-values/m-p/293061#M160464</link>
    <description>&lt;P&gt;We have multisite indexer cluster: two sites, 4 indexers per site (Splunk v. 6.5.3)&lt;BR /&gt;
Few months ago, following Splunk's recommendations, we increased ulimit  -n to a higher value 16384 on all indexers&lt;BR /&gt;
for root and splunk user. &lt;/P&gt;

&lt;P&gt;The following command "ulimit -n" returns "16384" on all 8 servers for both users now. &lt;BR /&gt;
To make these changes persistent across reboots our Unix SAs added this to the bottom of &lt;CODE&gt;/etc/security/limits.conf&lt;/CODE&gt;  file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunkuser soft nofile 16384
splunkuser  hard nofile 16384
root soft nofile 16384
root hard nofile 16384
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When we run health check via Splunk Monitoring Console, it finds that all 4 servers on site 1 have ulimits.open_files set to 4096 while&lt;BR /&gt;
ulimits.open_files set to 16384 on all  servers on site 2 &lt;/P&gt;

&lt;P&gt;What can be cause of this discrepancy ?&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 14:44:19 GMT</pubDate>
    <dc:creator>mlevsh</dc:creator>
    <dc:date>2020-09-29T14:44:19Z</dc:date>
    <item>
      <title>How does Splunk check for server ulimit values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-check-for-server-ulimit-values/m-p/293061#M160464</link>
      <description>&lt;P&gt;We have multisite indexer cluster: two sites, 4 indexers per site (Splunk v. 6.5.3)&lt;BR /&gt;
Few months ago, following Splunk's recommendations, we increased ulimit  -n to a higher value 16384 on all indexers&lt;BR /&gt;
for root and splunk user. &lt;/P&gt;

&lt;P&gt;The following command "ulimit -n" returns "16384" on all 8 servers for both users now. &lt;BR /&gt;
To make these changes persistent across reboots our Unix SAs added this to the bottom of &lt;CODE&gt;/etc/security/limits.conf&lt;/CODE&gt;  file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;splunkuser soft nofile 16384
splunkuser  hard nofile 16384
root soft nofile 16384
root hard nofile 16384
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When we run health check via Splunk Monitoring Console, it finds that all 4 servers on site 1 have ulimits.open_files set to 4096 while&lt;BR /&gt;
ulimits.open_files set to 16384 on all  servers on site 2 &lt;/P&gt;

&lt;P&gt;What can be cause of this discrepancy ?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:44:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-check-for-server-ulimit-values/m-p/293061#M160464</guid>
      <dc:creator>mlevsh</dc:creator>
      <dc:date>2020-09-29T14:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: How does Splunk check for server ulimit values?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-check-for-server-ulimit-values/m-p/293062#M160465</link>
      <description>&lt;P&gt;Duplicate post with: &lt;A href="https://answers.splunk.com/answers/552457/how-does-splunk-check-for-ulimit.html?childToView=551631#answer-551631"&gt;https://answers.splunk.com/answers/552457/how-does-splunk-check-for-ulimit.html?childToView=551631#answer-551631&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jun 2017 19:09:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/How-does-Splunk-check-for-server-ulimit-values/m-p/293062#M160465</guid>
      <dc:creator>guilmxm</dc:creator>
      <dc:date>2017-06-30T19:09:01Z</dc:date>
    </item>
  </channel>
</rss>

