Briefly, this error occurs when Elasticsearch tries to clean up unused elements, such as old indices or cache, but fails due to insufficient permissions, lack of disk space, or a locked file. To resolve this issue, you can try the following: 1) Check and adjust the permissions of the Elasticsearch directories. 2) Free up disk space or increase the disk capacity. 3) Identify and unlock the locked files that Elasticsearch is trying to clean. Always ensure to back up your data before performing these operations to prevent data loss.
This guide will help you check for common problems that cause the log ” Unable to clean unused element ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, repositories, repository-azure.
Overview
An Elasticsearch snapshot provides a backup mechanism that takes the current state and data in the cluster and saves it to a repository (read snapshot for more information). The backup process requires a repository to be created first. The repository needs to be registered using the _snapshot endpoint, and multiple repositories can be created per cluster. The following repository types are supported:
Repository types
| Repository type | Configuration type |
|---|---|
| Shared file system | Type: “fs” |
| S3 | Type : “s3” |
| HDFS | Type :“hdfs” |
| Azure | Type: “azure” |
| Google Cloud Storage | Type : “gcs” |
Examples
To register an “fs” repository:
PUT _snapshot/my_repo_01
{
"type": "fs",
"settings": {
"location": "/mnt/my_repo_dir"
}
}Notes and good things to know
- S3, HDFS, Azure and Google Cloud require a relevant plugin to be installed before it can be used for a snapshot.
- The setting, path.repo: /mnt/my_repo_dir needs to be added to elasticsearch.yml on all the nodes if you are planning to use the repo type of file system. Otherwise, it will fail.
- When using remote repositories, the network bandwidth and repository storage throughput should be high enough to complete the snapshot operations normally, otherwise you will end up with partial snapshots.
Log Context
Log “Unable to clean unused element” classname is CancellableRateLimitedFluxIterator.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
private void cleanElement(T element) {
try {
cleaner.accept(element);
} catch (Exception e) {
logger.warn("Unable to clean unused element"; e);
}
}
private void cancelSubscription() {
Subscription previousSubscription = subscription.getAndSet(CANCELLED_SUBSCRIPTION);
