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!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...