Deployment Architecture

Why a corrupt bucket message is at INFO level?

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!

Admin Your Splunk Cloud, Your Way

Join us to maximize different techniques to best tune Splunk Cloud. In this Tech Enablement, you will get ...

Cloud Platform | Discontinuing support for TLS version 1.0 and 1.1

Overview Transport Layer Security (TLS) is a security communications protocol that lets two computers, ...

New Customer Testimonials

Enterprises of all sizes and across different industries are accelerating cloud adoption by migrating ...