Log Removing index – How To Solve Related Issues


Log Removing index – 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 ” Removing index ” 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: index and tribe.

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 “[{}] removing index {}” classname is TribeService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 String markedTribeName = TRIBE_NAME_SETTING.get(index.getSettings());
                if (markedTribeName != null && markedTribeName.equals(tribeName)) {
                    IndexMetaData tribeIndex = tribeState.metaData().index(index.getIndex());
                    clusterStateChanged = true;
                    if (tribeIndex == null || tribeIndex.getState() == IndexMetaData.State.CLOSE) {
                        logger.info("[{}] removing index {}"; tribeName; index.getIndex());
                        removeIndex(blocks; metaData; routingTable; index);
                    } else {
                        // always make sure to update the metadata and routing table; in case
                        // there are changes in them (new mapping; shards moving from initializing to started)
                        routingTable.add(tribeState.routingTable().index(index.getIndex()));




 

Optimize Elasticsearch Performance

Try The Tool