<?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 Bucket replication queue full causing random indexer slowdown. in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Bucket-replication-queue-full-causing-random-indexer-slowdown/m-p/452689#M95716</link>
    <description>&lt;P&gt;Had a weird issue where my queues would fill up on random nodes and rove around within the cluster. &lt;BR /&gt;
Had a case opened with support  and Was working through and making all sorts of adjustments and ruling out all sorts of issues to no vail.&lt;BR /&gt;
Finally had a breakthrough when I noticed that we were seeing &lt;BR /&gt;
&lt;CODE&gt;INFO BucketReplicator - replication queue for peer=&amp;lt;guid&amp;gt; bid=&amp;lt;bid&amp;gt; is full&lt;/CODE&gt;. &lt;BR /&gt;
Followed almost immediately by &lt;BR /&gt;
&lt;CODE&gt;INFO BucketReplicator - replication queue for peer=&amp;lt;guid&amp;gt; bid=&amp;lt;bid&amp;gt; has room now.&lt;/CODE&gt; &lt;BR /&gt;
over and over again. The gap between those two messages was only a few milliseconds.&lt;/P&gt;

&lt;P&gt;No other obvious ERROR pointing to the cause.&lt;/P&gt;</description>
    <pubDate>Mon, 04 Feb 2019 20:16:07 GMT</pubDate>
    <dc:creator>sbhale</dc:creator>
    <dc:date>2019-02-04T20:16:07Z</dc:date>
    <item>
      <title>Bucket replication queue full causing random indexer slowdown.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Bucket-replication-queue-full-causing-random-indexer-slowdown/m-p/452689#M95716</link>
      <description>&lt;P&gt;Had a weird issue where my queues would fill up on random nodes and rove around within the cluster. &lt;BR /&gt;
Had a case opened with support  and Was working through and making all sorts of adjustments and ruling out all sorts of issues to no vail.&lt;BR /&gt;
Finally had a breakthrough when I noticed that we were seeing &lt;BR /&gt;
&lt;CODE&gt;INFO BucketReplicator - replication queue for peer=&amp;lt;guid&amp;gt; bid=&amp;lt;bid&amp;gt; is full&lt;/CODE&gt;. &lt;BR /&gt;
Followed almost immediately by &lt;BR /&gt;
&lt;CODE&gt;INFO BucketReplicator - replication queue for peer=&amp;lt;guid&amp;gt; bid=&amp;lt;bid&amp;gt; has room now.&lt;/CODE&gt; &lt;BR /&gt;
over and over again. The gap between those two messages was only a few milliseconds.&lt;/P&gt;

&lt;P&gt;No other obvious ERROR pointing to the cause.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 20:16:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Bucket-replication-queue-full-causing-random-indexer-slowdown/m-p/452689#M95716</guid>
      <dc:creator>sbhale</dc:creator>
      <dc:date>2019-02-04T20:16:07Z</dc:date>
    </item>
    <item>
      <title>Re: Bucket replication queue full causing random indexer slowdown.</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Bucket-replication-queue-full-causing-random-indexer-slowdown/m-p/452690#M95717</link>
      <description>&lt;P&gt;Answering my own question so others will find it useful.&lt;/P&gt;

&lt;P&gt;The presense of the above messages with the same peer guid was ruled to be the problem.&lt;BR /&gt;
One of our peer nodes was acting up and slowing down any nodes replicating to it just a little bit but enough that it was a propagating and causing queues to get backed up. &lt;BR /&gt;
The solution was putting the node in manual detention to be either re-built or retired.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 20:17:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Bucket-replication-queue-full-causing-random-indexer-slowdown/m-p/452690#M95717</guid>
      <dc:creator>sbhale</dc:creator>
      <dc:date>2019-02-04T20:17:58Z</dc:date>
    </item>
  </channel>
</rss>

