Log Adding index – How To Solve Related Issues


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

                 final IndexMetaData indexMetaData = currentState.metaData().index(indexName);
                if (indexMetaData == null) {
                    if (!droppedIndices.contains(indexName)) {
                        // a new index; add it; and add the tribe name as a setting
                        clusterStateChanged = true;
                        logger.info("[{}] adding index {}"; tribeName; tribeIndex.getIndex());
                        addNewIndex(tribeState; blocks; metaData; routingTable; tribeIndex);
                    }
                } else {
                    String existingFromTribe = TRIBE_NAME_SETTING.get(indexMetaData.getSettings());
                    if (!tribeName.equals(existingFromTribe)) {




 

Optimize Elasticsearch Performance

Try The Tool