<?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 High memory usage by Forwarders due to Indexer unavailability in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/High-memory-usage-by-Forwarders-due-to-Indexer-unavailability/m-p/508331#M86496</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We had a power outage after which our main Splunk instance (which serves as a Search Head and an Indexer) went offline, our Universal Forwarders installed on 2 Windows DC had both a huge memory usage after this causing one of these 2 hosts to crash.&lt;/P&gt;&lt;P&gt;I think the inability to forward events properly caused queues to fill, but checking output.conf file shows an existing reduction setting of their size limit : "maxQueueSize = 100KB" (default is 500KB).&lt;/P&gt;&lt;P&gt;My questions are :&lt;/P&gt;&lt;P&gt;1. What other steps can I take to prevent this ? (I prefer losing logs than having a critical host going offline).&lt;BR /&gt;2. Can I set a global memory usage limit for the Forwarders (like 2GB) ?&lt;BR /&gt;3. Could this be related to the Forwarders version (7.2.3) ?&lt;/P&gt;&lt;P&gt;I thank you in advance for your support.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jul 2020 15:38:40 GMT</pubDate>
    <dc:creator>yZinou</dc:creator>
    <dc:date>2020-07-09T15:38:40Z</dc:date>
    <item>
      <title>High memory usage by Forwarders due to Indexer unavailability</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/High-memory-usage-by-Forwarders-due-to-Indexer-unavailability/m-p/508331#M86496</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We had a power outage after which our main Splunk instance (which serves as a Search Head and an Indexer) went offline, our Universal Forwarders installed on 2 Windows DC had both a huge memory usage after this causing one of these 2 hosts to crash.&lt;/P&gt;&lt;P&gt;I think the inability to forward events properly caused queues to fill, but checking output.conf file shows an existing reduction setting of their size limit : "maxQueueSize = 100KB" (default is 500KB).&lt;/P&gt;&lt;P&gt;My questions are :&lt;/P&gt;&lt;P&gt;1. What other steps can I take to prevent this ? (I prefer losing logs than having a critical host going offline).&lt;BR /&gt;2. Can I set a global memory usage limit for the Forwarders (like 2GB) ?&lt;BR /&gt;3. Could this be related to the Forwarders version (7.2.3) ?&lt;/P&gt;&lt;P&gt;I thank you in advance for your support.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2020 15:38:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/High-memory-usage-by-Forwarders-due-to-Indexer-unavailability/m-p/508331#M86496</guid>
      <dc:creator>yZinou</dc:creator>
      <dc:date>2020-07-09T15:38:40Z</dc:date>
    </item>
  </channel>
</rss>

