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!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

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