Security

Applying indexing throttle for defaultdb\db because bucket has too many tsidx files, is your splunk-optimize working?

kholleran
Communicator

Hello,

I just recently upgraded from 4.1.3 to 4.1.5.

I also just added some fschange monitoring to inputs.conf and now after restart, I receive this in my SplunkWeb:

Applying indexing throttle for defaultdb\db because bucket has too many tsidx files, is your splunk-optimize working?

I have no idea what this means. Has anyone else seen this?

Thank you.

Kevin

Tags (2)
1 Solution

kholleran
Communicator

Had a corrupt bucket.

View solution in original post

jbsplunk
Splunk Employee
Splunk Employee
0 Karma

kholleran
Communicator

Had a corrupt bucket.

Get Updates on the Splunk Community!

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

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 ...