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!

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!

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

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...