<?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 Find the target indexer node responsible for causing indexqueue blocked across multiple source indexer nodes in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Find-the-target-indexer-node-responsible-for-causing-indexqueue/m-p/686921#M10019</link>
    <description>&lt;LI-CODE lang="markup"&gt;index=_internal source=*splunkd.log*  host=&amp;lt;all indexer hosts&amp;gt; bucketreplicator full earliest=-15m | stats count dc(host) as num_indexer_blocked_by_peer by peer | where num_indexer_blocked_by_peer &amp;gt; 0 AND count &amp;gt; 0 | join type=left peer [ search index=_introspection  host=&amp;lt;all indexer hosts&amp;gt; hostwide earliest=-10m | stats values(data.instance_guid) as peer by host]&lt;/LI-CODE&gt;</description>
    <pubDate>Wed, 08 May 2024 19:23:13 GMT</pubDate>
    <dc:creator>hrawat</dc:creator>
    <dc:date>2024-05-08T19:23:13Z</dc:date>
    <item>
      <title>Find the target indexer node responsible for causing indexqueue blocked across multiple source indexer nodes</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Find-the-target-indexer-node-responsible-for-causing-indexqueue/m-p/686921#M10019</link>
      <description>&lt;LI-CODE lang="markup"&gt;index=_internal source=*splunkd.log*  host=&amp;lt;all indexer hosts&amp;gt; bucketreplicator full earliest=-15m | stats count dc(host) as num_indexer_blocked_by_peer by peer | where num_indexer_blocked_by_peer &amp;gt; 0 AND count &amp;gt; 0 | join type=left peer [ search index=_introspection  host=&amp;lt;all indexer hosts&amp;gt; hostwide earliest=-10m | stats values(data.instance_guid) as peer by host]&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 08 May 2024 19:23:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Find-the-target-indexer-node-responsible-for-causing-indexqueue/m-p/686921#M10019</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2024-05-08T19:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: Find the target indexer node responsible for causing indexqueue blocked across multiple source indexer nodes</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Find-the-target-indexer-node-responsible-for-causing-indexqueue/m-p/751998#M10473</link>
      <description>&lt;P&gt;Now (10.x onwards) you can find the time target blocked.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=_internal bucketreplicator host=&amp;lt; all idx hosts&amp;gt; source=*splunkd.log*  total_blocked_time_seconds | timechart max(total_blocked_time_seconds) by peer

index=_internal bucketreplicator host=&amp;lt; all idx hosts&amp;gt; source=*splunkd.log*  total_blocked_time_seconds | timechart max(total_blocked_time_seconds) by bid&lt;/LI-CODE&gt;</description>
      <pubDate>Thu, 21 Aug 2025 19:28:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Find-the-target-indexer-node-responsible-for-causing-indexqueue/m-p/751998#M10473</guid>
      <dc:creator>hrawat</dc:creator>
      <dc:date>2025-08-21T19:28:01Z</dc:date>
    </item>
  </channel>
</rss>

