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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...