RecoveryStatus is used but it s refcount is 0 Probably a mismatch between incRef decRef – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when there’s a discrepancy in the reference count of RecoveryStatus in Elasticsearch. This could be due to improper handling of resources, leading to an imbalance between increment (incRef) and decrement (decRef) operations. To resolve this, ensure that for every incRef operation, there’s a corresponding decRef operation. Also, check your code for any possible leaks or premature decRef operations. Lastly, consider upgrading Elasticsearch to the latest version as this could be a bug that has been fixed in newer versions.

This guide will help you check for common problems that cause the log ” RecoveryStatus is used but it’s refcount is 0. Probably a mismatch between incRef/decRef ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery, indices.

Log Context

Log “RecoveryStatus is used but it’s refcount is 0. Probably a mismatch between incRef/decRef” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 return shardId + " [" + recoveryId + "]";
 }  private void ensureRefCount() {
 if (refCount() <= 0) {
 throw new ElasticsearchException("RecoveryStatus is used but it's refcount is 0. Probably a mismatch between incRef/decRef " +
 }  /*** Implementation of {@link RecoveryTargetHandler } */


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?