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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...