Completed closing of indices – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

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 has finished the process of closing indices. This is not necessarily an error, but more of an informational message indicating that the action of closing indices has been completed successfully. If this message is causing concern, you may want to check your Elasticsearch operations to ensure indices are not being closed unintentionally. To resolve this, you can reopen the closed indices using the open index API, or adjust your index lifecycle management policies to prevent indices from being closed if it’s not required.

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 ” completed closing of indices {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, indices, cluster.

Log Context

Log “completed closing of indices {}” classname is MetadataIndexStateService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                closedIndices.add(index.getName());
            } catch (final IndexNotFoundException e) {
                logger.debug("index {} has been deleted since it was blocked before closing; ignoring"; index);
            }
        }
        logger.info("completed closing of indices {}"; closedIndices);
        return Tuple.tuple(
            ClusterState.builder(currentState).blocks(blocks).metadata(metadata).routingTable(routingTable).build();
            List.copyOf(closingResults.values())
        );
    }

 

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?