Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 10 Mar 2016 15:21:40 +0000 (UTC)
From: "Michiel Vanderlee (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12948823.1457623291000.58842.1457623300749@Atlassian.JIRA>
In-Reply-To: <JIRA.12948823.1457623291000@Atlassian.JIRA>
References: <JIRA.12948823.1457623291000@Atlassian.JIRA>
 <JIRA.12948823.1457623291134@arcas>
Subject: [jira] [Created] (HADOOP-12914) RPC client should deal with the IP
 address change
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Michiel Vanderlee created HADOOP-12914:
------------------------------------------

             Summary: RPC client should deal with the IP address change
                 Key: HADOOP-12914
                 URL: https://issues.apache.org/jira/browse/HADOOP-12914
             Project: Hadoop Common
          Issue Type: Bug
          Components: ipc
    Affects Versions: 2.7.2
         Environment: CentOS 7
            Reporter: Michiel Vanderlee


I'm seeing HADOOP-7472 again for the datanode in v2.7.2.

If I start the datanode before the dns entry the namenode resolve, it never retries to resolve and keeps failing with a UnknownHostException.
A restart or the datanode fixes this.

TRACE ipc.ProtobufRpcEngine: 31: Exception <- nn1.hdfs-namenode-rpc.service.consul:8020: versionRequest {java.net.UnknownHostException: Invalid host name: local host is: (unknown); destination host is: "nn1.hdfs-namenode-rpc.service.consul":8020; java.net.UnknownHostException; For more details see:  http://wiki.apache.org/hadoop/UnknownHost}

The error comes from: 
org.apache.hadoop.ipc.Client..java$Connection line: 409

public Connection(ConnectionId remoteId, int serviceClass) throws IOException {
      this.remoteId = remoteId;
      this.server = remoteId.getAddress();
      if (server.isUnresolved()) {
        throw NetUtils.wrapException(server.getHostName(),
            server.getPort(),
            null,
            0,
            new UnknownHostException());
      }

The remoteId.address (InetSocketAddress) seems to only resolves on creation, never again unless done manually.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)