<?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 queue are getting blocked in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/queue-are-getting-blocked/m-p/483351#M82799</link>
    <description>&lt;P&gt;I have one Heavy forwarder and one indexer+search head. I am monitoring (high amount of) zip files in heavy forwarder and parsing it using indexqueue and null queue to reduce number of logs to reduce license cost. I am using Heavy forwarder used &lt;BR /&gt;
I am getting multiple queues blocked specially aggqueue(high number of times) though I have increased queue size but doesn't affect much.&lt;BR /&gt;
My Heavy forwarder has specification- windows OS , 64 gb RAM, 4 core&lt;/P&gt;

&lt;P&gt;also I am using below in props.conf- &lt;CODE&gt;line_breaker,should_linemerge,time_prefix,max_timestamp_lookahead, max_days_ago, time_format&lt;/CODE&gt;&lt;BR /&gt;
1. I know splunk will index zip files as single threaded so does increasing core will reduce queue blockage?&lt;BR /&gt;
2. also which queue is used to transfer files from heavy forwarder to indexer for indexing? so that I can check if that queue is getting full.&lt;BR /&gt;
3.what can be done to resolve queue blockage?  all queues are getting blocked at heavy forwarder side only.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2019 06:22:54 GMT</pubDate>
    <dc:creator>ips_mandar</dc:creator>
    <dc:date>2019-09-18T06:22:54Z</dc:date>
    <item>
      <title>queue are getting blocked</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/queue-are-getting-blocked/m-p/483351#M82799</link>
      <description>&lt;P&gt;I have one Heavy forwarder and one indexer+search head. I am monitoring (high amount of) zip files in heavy forwarder and parsing it using indexqueue and null queue to reduce number of logs to reduce license cost. I am using Heavy forwarder used &lt;BR /&gt;
I am getting multiple queues blocked specially aggqueue(high number of times) though I have increased queue size but doesn't affect much.&lt;BR /&gt;
My Heavy forwarder has specification- windows OS , 64 gb RAM, 4 core&lt;/P&gt;

&lt;P&gt;also I am using below in props.conf- &lt;CODE&gt;line_breaker,should_linemerge,time_prefix,max_timestamp_lookahead, max_days_ago, time_format&lt;/CODE&gt;&lt;BR /&gt;
1. I know splunk will index zip files as single threaded so does increasing core will reduce queue blockage?&lt;BR /&gt;
2. also which queue is used to transfer files from heavy forwarder to indexer for indexing? so that I can check if that queue is getting full.&lt;BR /&gt;
3.what can be done to resolve queue blockage?  all queues are getting blocked at heavy forwarder side only.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2019 06:22:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/queue-are-getting-blocked/m-p/483351#M82799</guid>
      <dc:creator>ips_mandar</dc:creator>
      <dc:date>2019-09-18T06:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: queue are getting blocked</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/queue-are-getting-blocked/m-p/483352#M82800</link>
      <description>&lt;P&gt;You can see the role of queues here.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://wiki.splunk.com/Community:HowIndexingWorks"&gt;https://wiki.splunk.com/Community:HowIndexingWorks&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Since there is only one process, the queue accumulates when processing large logs. Even if the number of cores increases, improvement cannot be expected.&lt;/P&gt;

&lt;P&gt;Splunk can multiplex processes. See the link below. &lt;/P&gt;

&lt;P&gt;&lt;A href="https://conf.splunk.com/files/2016/slides/harnessing-performance-and-scalability-with-parallelization.pdf"&gt;https://conf.splunk.com/files/2016/slides/harnessing-performance-and-scalability-with-parallelization.pdf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Multiplexing is limited to two. Professional service is required when setting to 3 multiplex.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2019 07:28:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/queue-are-getting-blocked/m-p/483352#M82800</guid>
      <dc:creator>HiroshiSatoh</dc:creator>
      <dc:date>2019-09-18T07:28:28Z</dc:date>
    </item>
  </channel>
</rss>

