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!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...