Log Unexpected failure during ; current state:n – How To Solve Related Issues



Log Unexpected failure during ; current state:n – 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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Unexpected failure during ; current state:n” 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, routing.


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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log “Unexpected failure during [{}]; current state:n{}” classname is RoutingService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     
Override
                    public void onFailure(String source; Exception e) {
                        rerouting.set(false);
                        ClusterState state = clusterService.state();
                        if (logger.isTraceEnabled()) {
                            logger.error(() -> new ParameterizedMessage("unexpected failure during [{}]; current state:\n{}";
                                source; state); e);
                        } else {
                            logger.error(() -> new ParameterizedMessage("unexpected failure during [{}]; current state version [{}]";
                                source; state.version()); e);
                        }








Find Configuration Errors

Try The Tool