<?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 Re: High Memory on Indexers in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/High-Memory-on-Indexers/m-p/504855#M2022</link>
    <description>&lt;P&gt;If you are starting splunk with systemd, then you must update it’s config to use new additional memory. Just disable and then enable boot start or directly edit systemd startup config.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jun 2020 19:53:52 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2020-06-17T19:53:52Z</dc:date>
    <item>
      <title>High Memory on Indexers</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/High-Memory-on-Indexers/m-p/504830#M2018</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have recently upgraded Splunk memory to 64 GB. I am observing strange behavior that capacity is consuming 90% of the memory. I am seeing the same behavior for past one year where i have increased the RAM from 16 GB to 64 GB Now.&lt;/P&gt;&lt;P&gt;Most of the memory is cache. Can anyone let me know if this is normal behaviour of Indexers with High memory along with cache.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2020 16:23:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/High-Memory-on-Indexers/m-p/504830#M2018</guid>
      <dc:creator>dvohra</dc:creator>
      <dc:date>2020-06-17T16:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: High Memory on Indexers</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/High-Memory-on-Indexers/m-p/504855#M2022</link>
      <description>&lt;P&gt;If you are starting splunk with systemd, then you must update it’s config to use new additional memory. Just disable and then enable boot start or directly edit systemd startup config.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2020 19:53:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/High-Memory-on-Indexers/m-p/504855#M2022</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2020-06-17T19:53:52Z</dc:date>
    </item>
  </channel>
</rss>

