<?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: What should the indexer queues be? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/What-should-the-indexer-queues-be/m-p/410368#M72721</link>
    <description>&lt;P&gt;Support said - &lt;/P&gt;

&lt;P&gt;-- What i assume is occurring based on which Q's are full is that you have a bad regex somewhere, or for a particular source type the event breaking is not working, &lt;STRONG&gt;so for the event breaking not working, the forwarder locks onto an indexer&lt;/STRONG&gt; and does not let it loadbalance as it feels it has not reached the end of the event.&lt;/P&gt;

&lt;P&gt;And we found out that there was a weird &lt;CODE&gt;LINE_BREAKER&lt;/CODE&gt; set for a new sourcetype. Removing it and the queues got cleared. &lt;/P&gt;</description>
    <pubDate>Tue, 30 Jul 2019 14:15:37 GMT</pubDate>
    <dc:creator>danielbb</dc:creator>
    <dc:date>2019-07-30T14:15:37Z</dc:date>
    <item>
      <title>What should the indexer queues be?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-should-the-indexer-queues-be/m-p/410367#M72720</link>
      <description>&lt;P&gt;After filling the tiny queues on the indexers, we would like to move to bigger queues. &lt;/P&gt;

&lt;P&gt;We are thinking about the following -&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[queue=AQ]
# Default maxSize = 10MB
maxSize = 200MB

[queue=aggQueue]
# Default maxSize = 1MB
maxSize = 3500MB

[queue=parsingQueue]
# Default maxSize = 6MB
maxSize = 3600MB

[queue=typingQueue]
maxSize = 2100MB

[queue=indexQueue]
maxSize = 4000MB
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Does it make sense?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2019 12:39:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-should-the-indexer-queues-be/m-p/410367#M72720</guid>
      <dc:creator>danielbb</dc:creator>
      <dc:date>2019-07-30T12:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: What should the indexer queues be?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/What-should-the-indexer-queues-be/m-p/410368#M72721</link>
      <description>&lt;P&gt;Support said - &lt;/P&gt;

&lt;P&gt;-- What i assume is occurring based on which Q's are full is that you have a bad regex somewhere, or for a particular source type the event breaking is not working, &lt;STRONG&gt;so for the event breaking not working, the forwarder locks onto an indexer&lt;/STRONG&gt; and does not let it loadbalance as it feels it has not reached the end of the event.&lt;/P&gt;

&lt;P&gt;And we found out that there was a weird &lt;CODE&gt;LINE_BREAKER&lt;/CODE&gt; set for a new sourcetype. Removing it and the queues got cleared. &lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2019 14:15:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/What-should-the-indexer-queues-be/m-p/410368#M72721</guid>
      <dc:creator>danielbb</dc:creator>
      <dc:date>2019-07-30T14:15:37Z</dc:date>
    </item>
  </channel>
</rss>

