What do I do with buckets?
Buckets are portions of Splunk indexes. This article points you to a few resources for troubleshooting problems with buckets.
Might I be having issues with bucket rotation?
An unsuitable bucket rotation and retention policy can lead to:
- old events being deleted before they reach frozen buckets,
- hot and warm buckets filling up, stopping Splunk,
- old events not being archived correctly and thus still searchable when they shouldn't be, and
- poor searching or indexing performance.
Here's a Community Wiki article about bucket rotation and retention with specific recommendations and examples.
Recover metadata for a corrupt Splunk index directory
Contact Splunk Support for direction before using this command.
recover-metadata command recovers missing or corrupt metadata associated with any Splunk index directory, sometimes also referred to as a bucket.
If your Splunk instance will not start, a possible cause is that one or more of your index buckets is corrupt in some way. Contact Support; they will help you determine if this is indeed the case and if so, which bucket(s) are affected. Then, run this command:
$SPLUNK_HOME/bin/splunk cmd recover-metadata <full path to the exact index directory/bucket>
Splunk returns a success or failure message.
Recovering and rebuilding buckets
The Managing Indexers and Clusters Manual has a thorough explanation of buckets. This section of "How Splunk stores indexes" tells you how to troubleshoot bucket problems, like recovering after a crash and rebuilding buckets. You'll probably want to read from the start of that page, though, to get some background first.
Binary file error
Troubleshoot Windows event log collection
This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.0.15, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.1.14