Deployment Architecture
×

Join the Conversation

Without signing in, you're just watching from the sidelines. Sign in or Register to connect, share, and be part of the Splunk Community.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Ask a Question

Why a corrupt bucket message is at INFO level?

ddrillic
Ultra Champion
‎02-04-2018 08:10 AM

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
Reply
Get Updates on the Splunk Community!

New Year, New Changes for Splunk Certifications

As we embrace a new year, we’re making a small but important update to the Splunk Certification ...

Stay Connected: Your Guide to January Tech Talks, Office Hours, and Webinars!

What are Community Office Hours? Community Office Hours is an interactive 60-minute Zoom series where ...

[Puzzles] Solve, Learn, Repeat: Reprocessing XML into Fixed-Length Events

This challenge was first posted on Slack #puzzles channelFor a previous puzzle, I needed a set of fixed-length ...