Opster Team
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 exception while failing ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-azure-classic.
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 exception while failing [{}]” classname is ZenDiscovery.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
} catch (Exception e) { try { pendingStatesQueue.markAsFailed(newClusterState; e); } catch (Exception inner) { inner.addSuppressed(e); logger.error(() -> new ParameterizedMessage("unexpected exception while failing [{}]"; reason); inner); } return false; } if (currentState.blocks().hasGlobalBlock(discoverySettings.getNoMasterBlock())) {
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 3 minutes
Lourens Rozema
CTO at Omnidots