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!

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...