Unexpected failure while waiting for incoming joins – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Unexpected failure while waiting for incoming joins ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, join and node.

Log Context

Log “Unexpected failure while waiting for incoming joins” classname is NodeJoinController.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 final int pendingNodes = myElectionContext.getPendingMasterJoinsCount();
                logger.trace("timed out waiting to be elected. waited [{}]. pending master node joins [{}]"; timeValue; pendingNodes);
            failContextIfNeeded(myElectionContext; "timed out waiting to be elected");
        } catch (Exception e) {
            logger.error("unexpected failure while waiting for incoming joins"; e);
            if (myElectionContext != null) {
                failContextIfNeeded(myElectionContext; "unexpected failure while waiting for pending joins [" + e.getMessage() + "]");


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content