<?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 parallelIngestionPipelines on heavy forwarder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/parallelIngestionPipelines-on-heavy-forwarder/m-p/382990#M68988</link>
    <description>&lt;P&gt;hi, &lt;BR /&gt;
we have activated parallelIngestionPipelines (set to 2) due to blocked queues on a heavy forwarder. After adding another pipeline, there is no change in the congestion and it seems that only one pipeline is used by Splunk. &lt;BR /&gt;
Pipeline 0  still gets blocked and filled to 100% and pipeline 1 processes only on rare occasions, usually filled to 0 %. Any idea what could cause this unexptected behavior?&lt;/P&gt;</description>
    <pubDate>Wed, 13 Jun 2018 15:41:45 GMT</pubDate>
    <dc:creator>mraudaschl</dc:creator>
    <dc:date>2018-06-13T15:41:45Z</dc:date>
    <item>
      <title>parallelIngestionPipelines on heavy forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/parallelIngestionPipelines-on-heavy-forwarder/m-p/382990#M68988</link>
      <description>&lt;P&gt;hi, &lt;BR /&gt;
we have activated parallelIngestionPipelines (set to 2) due to blocked queues on a heavy forwarder. After adding another pipeline, there is no change in the congestion and it seems that only one pipeline is used by Splunk. &lt;BR /&gt;
Pipeline 0  still gets blocked and filled to 100% and pipeline 1 processes only on rare occasions, usually filled to 0 %. Any idea what could cause this unexptected behavior?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jun 2018 15:41:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/parallelIngestionPipelines-on-heavy-forwarder/m-p/382990#M68988</guid>
      <dc:creator>mraudaschl</dc:creator>
      <dc:date>2018-06-13T15:41:45Z</dc:date>
    </item>
  </channel>
</rss>

