Deployment Architecture

"Got Done key for an unknown bucket without getting any data"

nickhills
Ultra Champion

I have a MultiSite indexing cluster, and a single Peer int site 2 is repeatedly reporting:

ERROR TcpInputProc - event=replicationData status=failed err="Got Done key for an unknown bucket without getting any data"

150 or so times at once.

restarting the peer (with cluster maint mode set) has had no effect.

Obviously there is no indication if this is one bucket many times, or lots of buckets.
I'm at a bit of loss how to diagnose further, but wonder if I should stop the indexer and let the cluster fixup, and then bring the indexer back online, unless anyone can provide a more scientific approach.

If my comment helps, please give it a thumbs up!

bohanlon_splunk
Splunk Employee
Splunk Employee

Reading this might help:
https://docs.splunk.com/Documentation/Splunk/6.5.2/Indexer/Anomalousbuckets

This query might also be useful:

| rest /services/cluster/master/info 
| fields buckets_to_fix.*.latest.reason 
| transpose 
| rename column AS bucket "row 1" AS reason 
| rex field=bucket "buckets_to_fix\.(?.*?)\.latest\.reason" 
| rex field=bucket "(?[^~]*?)~" 
| rex mode=sed field=reason "s/[0-9A-Z]{8}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{12}/{PEER}/" 
0 Karma

DalJeanis
Legend

@bohanlon [Splunk] - marked the query code but it's still missing the tags. Line 4 looks odd, too, please repost.

0 Karma
Get Updates on the Splunk Community!

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...

State of Splunk Careers 2024: Maximizing Career Outcomes and the Continued Value of ...

For the past four years, Splunk has partnered with Enterprise Strategy Group to conduct a survey that gauges ...

Data-Driven Success: Splunk & Financial Services

Splunk streamlines the process of extracting insights from large volumes of data. In this fast-paced world, ...