Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.
Briefly, this error occurs when Elasticsearch fails to remove retention leases, which are used to retain operations for a certain period of time. This could be due to a network issue, a node failure, or a problem with the underlying storage. To resolve this issue, you can try restarting the Elasticsearch node, checking the network connectivity, or inspecting the health of the underlying storage system. If the problem persists, you may need to manually remove the retention leases using the Elasticsearch API.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” es.failed_to_remove_retention_leases ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “es.failed_to_remove_retention_leases” class name is UnfollowFollowerIndexStep.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (r.isAcknowledged() == false) {
throw new ElasticsearchException("unfollow request failed to be acknowledged");
}
listener.onResponse(null);
}; exception -> {
if (exception instanceof ElasticsearchException e && e.getMetadata("es.failed_to_remove_retention_leases") != null) {
List leasesNotRemoved = e.getMetadata("es.failed_to_remove_retention_leases");
logger.debug(
"failed to remove leader retention lease(s) {} while unfollowing index [{}]; " + "continuing with lifecycle execution";
leasesNotRemoved;
followerIndex
