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

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

                         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);
                        }
                    }
                });
        } catch (Exception e) {




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content