Log Failed to set for index ; it should be dash delimited – How To Solve Related Issues


Log Failed to set for index ; it should be dash delimited – How To Solve Related Issues

Opster Team

Feb-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 ” Failed to set for index ; it should be dash delimited ” 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, metadata and settings.

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 “failed to set [{}] for index [{}]; it should be dash delimited [{}]” classname is MetaDataUpdateSettingsService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     final int min;
                    final int max;

                    final int dash = autoExpandReplicas.indexOf('-');
                    if (-1 == dash) {
                        logger.warn("failed to set [{}] for index [{}]; it should be dash delimited [{}]";
                                IndexMetaData.SETTING_AUTO_EXPAND_REPLICAS; indexMetaData.getIndex(); autoExpandReplicas);
                        continue;
                    }
                    final String sMin = autoExpandReplicas.substring(0; dash);
                    try {




 

Optimize Elasticsearch Performance

Try The Tool