Splunk Dev

Buckets stuck in fixup for non-streaming failure

wcates
Explorer

We upgraded our Splunk instance and now we have two buckets stuck in fixup for a non-streaming failure. It shows that it exists on 2 of our 3 indexers, and neither resyncing nor rolling the buckets fixes the problem. When I look in the folder on the indexer that it does not show the bucket existing on, I see a folder for the bucket with rawdata in it. Every minute the time in fixup is resetting. Has anyone encountered this problem before and been able to fix it?

Tags (1)
0 Karma
1 Solution

wcates
Explorer

After 3 days the error has miraculously disappeared, so anyone who has this issue in the future maybe waiting is the only option.

View solution in original post

0 Karma

wcates
Explorer

After 3 days the error has miraculously disappeared, so anyone who has this issue in the future maybe waiting is the only option.

0 Karma
Get Updates on the Splunk Community!

Your Guide to Splunk Digital Experience Monitoring

A flawless digital experience isn't just an advantage, it's key to customer loyalty and business success. But ...

Data Management Digest – November 2025

  Welcome to the inaugural edition of Data Management Digest! As your trusted partner in data innovation, the ...

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...