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 can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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());



Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content