Unexpected failure during ; current state:n – How to solve related issues

Average Read Time

2 Mins

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 run 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 ” Unexpected failure during ; current state:n ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and routing.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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);
                        }



 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content