Deployment Architecture

Why a corrupt bucket message is at INFO level?

ddrillic
Ultra Champion

Yesterday one of our production indexer stopped indexing for 12 hours. Support found the cause to be a corrupt bucket.

The message in splunkd.log was -

splunkd.log.2:02-03-2018 07:28:50.526 -0600 INFO  HotBucketRoller - Bucket='/SplunkIndexData/splunk-indexes/<index name>/db/db_1517657319_1517657289_15604', idx=<index name>, newly --all **corrupt**: reason=''

I wonder why a corrupt bucket message, which causes the indexer to stop indexing, is marked only as INFO.

Tags (2)
0 Karma
Get Updates on the Splunk Community!

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

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...