Log Closing indices – How To Solve Related Issues


Log Closing indices – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the 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 ” Closing indices ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log context

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

             }
            blocks.addIndexBlock(index.getName(); indexBlock);
            blockedIndices.put(index; indexBlock);
        }

        logger.info(() -> new ParameterizedMessage("closing indices {}";
            blockedIndices.keySet().stream().map(Object::toString).collect(Collectors.joining(";"))));
        return ClusterState.builder(currentState).blocks(blocks).metaData(metadata).routingTable(routingTable.build()).build();
    }

    /**




 

Optimize Elasticsearch Performance

Try The Tool