No instance available for ; ignoring. – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” No instance available for ; ignoring. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “[{}] no instance available for [{}]; ignoring…” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

      * NOTE: this method swallows all exceptions thrown from the close method of the injector and logs them as debug log
    private void closeInjectorResource(ShardId shardId; Injector shardInjector; Class extends Closeable>... toClose) {
        for (Class extends Closeable> closeable : toClose) {
            if (closeInjectorOptionalResource(shardId; shardInjector; closeable) == false) {
                logger.warn("[{}] no instance available for [{}]; ignoring... "; shardId; closeable.getSimpleName());



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?

Analyze your cluster & get personalized recommendations

Skip to content