Received a wrong address type from ignoring – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch receives an unexpected address type from a node it’s trying to communicate with. This could be due to a misconfiguration in the network settings or a mismatch in the versions of Elasticsearch running on different nodes. To resolve this issue, you can check and correct the network settings, ensure all nodes are running the same version of Elasticsearch, or check the cluster health to identify any problematic nodes and address the issues.

This guide will help you check for common problems that cause the log ” received a wrong address type from [{}]; ignoring… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery.

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


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?