Anomalous bucket issues
Anomalous buckets are buckets that remain in the fixup state indefinitely, without making any progress. Such buckets can indicate or cause a larger problem with your system. An anomalous bucket, for example, can prevent the cluster from meeting its replication and search factors.
The Bucket Status dashboard lets you identify anomalous buckets. It also allows you to take actions on those buckets that can often fix them. Specifically, you can:
- Get details on a bucket.
- Roll the bucket from hot to warm.
- Resync the state of a bucket copy between a peer and the master.
- Delete a copy of the bucket on a single peer, or delete all copies of the bucket across all peers.
Consult with Splunk Support before performing these actions on a bucket. Some of the actions, performed without full understanding, can lead to further problems with your system or even to irreversible data loss.
Identify anomalous buckets
To identify anomalous buckets and to take action on them, use the Bucket Status dashboard.
- From the Master dashboard, go to the Bucket Status dashboard. See View the bucket status dashboard.
- Click the Fixup Tasks - Pending tab.
You can filter the list of pending buckets by fixup type and by the amount of time that they have been waiting for fixup. If a bucket has been waiting an unusual amount of time for fixup, it might be the cause of problems.
Take action on an anomalous bucket
For buckets that have been stuck in fixup for long periods of time, you can take remedial action.
- Click Action for the bucket that you want to manage.
- Select one of the available actions:
- View bucket details
- Delete Copy
Use the following sequence when performing actions on anomalous bucket.
- View bucket details
- Delete Copy
Only perform the next action if the previous one does not resolve the issue.
View bucket details
This pop-up window provides details on the bucket such as:
- The bucket size
- Whether it is frozen
- Whether it has been force-rolled
- Whether it is a standalone bucket
- The peers on which it resides
These details can help to narrow down the cause of the bucket problem and what action to take to remediate it.
This action rolls the bucket from the hot state to the warm state. It has an effect only on hot buckets.
The master holds information about each copy of a bucket. However, in some cases, the master can have incorrect information about the copy on a particular peer. This condition can occur when communication problems arise between the master and a peer.
Here are some examples of bucket copy state information that can be out of sync between peer and master:
- Whether the copy is searchable
- Whether the copy is hot or warm
- Whether the copy is primary
- Whether the copy exists on that peer
The peer knows the state of its bucket copies, so if the peer and the master have different state information for a bucket copy, the information on the master is incorrect.
To resolve this problem, resync the bucket copy's state on the master. When you resync a bucket, you specify the peer with the copy that you need to resync. The resync process causes the peer to send the master its current information about the bucket copy.
You can delete either a single copy of a bucket on a specific peer, or all copies of a bucket across the entire cluster.
If deleting a single copy causes the cluster to lose its complete state, the cluster will engage in fixup activities so that the bucket again meets both the search factor and the replication factor. This situation might result in another copy of the bucket appearing on the same peer. If, however, the specified bucket is frozen, the cluster does not attempt any fixup activities.
Performing the delete action on all copies of a bucket across the cluster results in irreversible data loss.
Bucket replication issues
Configuration bundle issues
This documentation applies to the following versions of Splunk® Enterprise: 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.3.0