Knowledge Management

Find the target indexer node responsible for causing indexqueue blocked across multiple source indexer nodes

hrawat
Splunk Employee
Splunk Employee
index=_internal source=*splunkd.log*  host=<all indexer hosts> bucketreplicator full earliest=-15m | stats count dc(host) as num_indexer_blocked_by_peer by peer | where num_indexer_blocked_by_peer > 0 AND count > 0 | join type=left peer [ search index=_introspection  host=<all indexer hosts> hostwide earliest=-10m | stats values(data.instance_guid) as peer by host]
Tags (1)

hrawat
Splunk Employee
Splunk Employee

Now (10.x onwards) you can find the time target blocked.

index=_internal bucketreplicator host=< all idx hosts> source=*splunkd.log*  total_blocked_time_seconds | timechart max(total_blocked_time_seconds) by peer

index=_internal bucketreplicator host=< all idx hosts> source=*splunkd.log*  total_blocked_time_seconds | timechart max(total_blocked_time_seconds) by bid
Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...