Received a wrong address type from ; ignoring. – How to solve related issues

Average Read Time

2 Mins

Received a wrong address type from ; ignoring. – How to solve related issues

Opster Team

Feb-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 ” Received a wrong address type from ; ignoring. ” 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: discovery.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context


Log “received a wrong address type from [{}]; ignoring…” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    void handleJoinRequest(final DiscoveryNode node; final ClusterState state; final MembershipAction.JoinCallback callback) {

        if (!transportService.addressSupported(node.address().getClass())) {
            // TODO; what should we do now? Maybe inform that node that its crap?
            logger.warn("received a wrong address type from [{}]; ignoring..."; node);
        } else if (nodeJoinController == null) {
            throw new IllegalStateException("discovery module is not yet started");
        } else {
            // The minimum supported version for a node joining a master:
            Version minimumNodeJoinVersion = localNode().getVersion().minimumCompatibilityVersion();


Run the Check-Up to get a customized report like this:

Analyze your cluster