bucket error "Leaving it in PendingDiscard state."

[sbaryakov]

I'm looking for documentation about the following error:

"Discarding bid=foo~0~60F537A5-5D22-4F24-81FD-000544991297 on peer=8E98E68C-5240-4298-9B79-AAFC9C42B2A7 failed. Leaving it in PendingDiscard state."

The error appears on the manager UI in clustered splunk 5.0.3 for a clustered bucket

Thank you!

[theunf]

If there´s nothing wrong with the data or the integrity of the bucket, can the master request an indexer to discard a bucket just by interpreeting that does not belong to that cluster ?

I´m trying to follow a probable scenario where peers were migrated from one master to the other and the new master seems to make the error to ask the peers to discard buckets and that lead to a loss of data.

That happened with 3 peers that were replicating information normally and the master move were needed due to hardware failure on the master and on 2 other peers.

[rturk · Accepted solution]

Hi Sbaryakov,

From what I can gather, the Cluster Master has requested one of your search peers/indexers to discard a bucket, and is awaiting confirmation that this has happened. It may be worthwhile looking at the internal logs on the indexer to see if there are any potential issues there.

A little late I know, but I hope this helps 🙂

Reference:

• http://docs.splunk.com/Documentation/Splunk/5.0.4/RESTAPI/RESTcluster