<?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: Parsing queue and Aggregation queue sizes on heavy forwarders? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316245#M93247</link>
    <description>&lt;P&gt;@jihape - Was your issue resolved? I am in the same boat looking for a safe shore.&lt;/P&gt;</description>
    <pubDate>Mon, 26 Aug 2019 01:16:00 GMT</pubDate>
    <dc:creator>nareshinsvu</dc:creator>
    <dc:date>2019-08-26T01:16:00Z</dc:date>
    <item>
      <title>Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316241#M93243</link>
      <description>&lt;P&gt;We are seeing the aggregation and parsing queues almost constantly flatlining at a 100% on our HFs. On our indexers the queues are at 0% pretty much all the time, with the occasional spike to 20%.&lt;/P&gt;

&lt;P&gt;Would increasing the &lt;CODE&gt;[queue=parsingQueue]&lt;/CODE&gt; and &lt;CODE&gt;[queue=aggQueue]&lt;/CODE&gt; in &lt;CODE&gt;system/local/server.conf&lt;/CODE&gt; help lowering the queue fill ratio? The current settings are the default 6MB for Parsing and 1MB for aggregation.&lt;/P&gt;

&lt;P&gt;There are only 250 UFs connected to the HF, but that is expected to increase dramatically.&lt;/P&gt;

&lt;P&gt;If increasing the queue size works, by how much should I increase it? Is there a rule of thumb that I haven't seen?&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 00:15:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316241#M93243</guid>
      <dc:creator>jihape</dc:creator>
      <dc:date>2018-03-01T00:15:50Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316242#M93244</link>
      <description>&lt;P&gt;The load on the indexer is low and the queue is formed on the HF side is a problem in the processing on the HF side.&lt;BR /&gt;
Increasing the size of the queue does not solve the problem. Please first check high load processing.&lt;BR /&gt;
For example, the transfer rate (maxKBps) may be low.Also, if the parsing process is slow, it is also possible to increase the pipeline.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 03:17:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316242#M93244</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2018-03-01T03:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316243#M93245</link>
      <description>&lt;P&gt;Thanks, I couldn't identify any issues with the server:&lt;BR /&gt;
1. It was not a CPU issue - max CPU was only 50%&lt;BR /&gt;
2. transfer rate in &lt;CODE&gt;limits.conf&lt;/CODE&gt; is set to &lt;CODE&gt;0&lt;/CODE&gt;&lt;BR /&gt;
3. Is it this settings you are talking about when saying 'increase the pipeline'? &lt;A href="http://docs.splunk.com/Documentation/Splunk/7.0.2/Capacity/Parallelization#Index_parallelization"&gt;http://docs.splunk.com/Documentation/Splunk/7.0.2/Capacity/Parallelization#Index_parallelization&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 03:56:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316243#M93245</guid>
      <dc:creator>jihape</dc:creator>
      <dc:date>2018-03-01T03:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316244#M93246</link>
      <description>&lt;P&gt;Yes. The pipeline is that. Processes can be parallelized. But up to two. More than (3 or more  require PS.&lt;/P&gt;

&lt;P&gt;Can you investigate high load queues?&lt;BR /&gt;
setting&amp;gt;monitoring console&amp;gt;Indexing&amp;gt;Indexing Performance: Instance&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 05:13:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316244#M93246</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2018-03-01T05:13:04Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316245#M93247</link>
      <description>&lt;P&gt;@jihape - Was your issue resolved? I am in the same boat looking for a safe shore.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Aug 2019 01:16:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/316245#M93247</guid>
      <dc:creator>nareshinsvu</dc:creator>
      <dc:date>2019-08-26T01:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/604608#M105143</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/143705"&gt;@jihape&lt;/a&gt;,&amp;nbsp; have you solved this issue? We are facing the same problem...&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2022 15:23:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/604608#M105143</guid>
      <dc:creator>justynap_ldz</dc:creator>
      <dc:date>2022-07-06T15:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/627779#M107734</link>
      <description>&lt;P&gt;Facing this same issue with few servers.&lt;BR /&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/143705"&gt;@jihape&lt;/a&gt;&amp;nbsp;Have you found the solution of it? How did you fix it?&lt;BR /&gt;&lt;BR /&gt;I have just added the this setting `&lt;SPAN&gt;parallelIngestionPipelines=2` and increased the parsingqueue on HF from 1024MB to 2048MB. Would this solve the issue?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 16:00:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/627779#M107734</guid>
      <dc:creator>sohaib112</dc:creator>
      <dc:date>2023-01-20T16:00:31Z</dc:date>
    </item>
    <item>
      <title>Re: Parsing queue and Aggregation queue sizes on heavy forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/627839#M107738</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;how many HFs you have vs indexers? I have seen a rule of thumb that you should have (min) 7 hf pipeline per one IDX pipeline to get this working smoothly.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jan 2023 21:48:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Parsing-queue-and-Aggregation-queue-sizes-on-heavy-forwarders/m-p/627839#M107738</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-01-20T21:48:59Z</dc:date>
    </item>
  </channel>
</rss>

