Completed closing of indices – How to solve related issues

Opster Team

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

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 “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 ClusterState.builder(currentState).blocks(blocks).metaData(metadata).routingTable(routingTable.build()).build();
    }

    public void openIndex(final OpenIndexClusterStateUpdateRequest request;
                          final ActionListener listener) {




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content