You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2015/10/28 01:29:27 UTC

[jira] [Created] (HADOOP-12522) Simplify adding NN service RPC port to an existing HA cluster with ZKFCs

Arpit Agarwal created HADOOP-12522:
--------------------------------------

             Summary: Simplify adding NN service RPC port to an existing HA cluster with ZKFCs
                 Key: HADOOP-12522
                 URL: https://issues.apache.org/jira/browse/HADOOP-12522
             Project: Hadoop Common
          Issue Type: Bug
          Components: ha
    Affects Versions: 2.7.1
            Reporter: Arpit Agarwal
            Assignee: Arpit Agarwal


ZKFCs fail the following check in {{DFSZKFailoverController#dataToTarget}} if an NN service RPC port is added to an existing cluster.

{code}
  protected HAServiceTarget dataToTarget(byte[] data) {
...    
    if (!addressFromProtobuf.equals(ret.getAddress())) {
      throw new RuntimeException("Mismatched address stored in ZK for " +
          ret + ": Stored protobuf was " + proto + ", address from our own " +
          "configuration for this NameNode was " + ret.getAddress());
    }

{code}

The NN address stored in the znode had the common client+service RPC port number whereas the configuration now returns an address with the service RPC port. The workaround is to reformat the ZKFC state in ZK with {{hdfs zkfc -formatZK}}.



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