You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2012/05/25 20:44:23 UTC

[jira] [Created] (HDFS-3465) 2NN doesn't start with fs.defaultFS set to a viewfs URI unless service RPC address is also set

Eli Collins created HDFS-3465:
---------------------------------

             Summary: 2NN doesn't start with fs.defaultFS set to a viewfs URI unless service RPC address is also set
                 Key: HDFS-3465
                 URL: https://issues.apache.org/jira/browse/HDFS-3465
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: name-node
    Affects Versions: 2.0.0-alpha
            Reporter: Eli Collins


Looks like the 2NN first tries servicerpc-address then falls back on fs.defaultFS, which won't work in the case of federation since fs.defaultFS doesn't refer to an RPC address. Instead, the 2NN should first check servicerpc-address, then rpc-address, then fall back on fs.defaultFS.

{noformat}
Exception in thread "main" java.lang.IllegalArgumentException: Invalid
URI for NameNode address (check fs.defaultFS): viewfs:/// has no
authority.
       at org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:315)
       at org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:303)
       at org.apache.hadoop.hdfs.server.namenode.NameNode.getServiceAddress(NameNode.java:296)
       at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:214)
       at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.<init>(SecondaryNameNode.java:178)
       at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.main(SecondaryNameNode.java:582)
{noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HDFS-3465) 2NN doesn't start with fs.defaultFS set to a viewfs URI unless service RPC address is also set

Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eli Collins updated HDFS-3465:
------------------------------

    Component/s: federation
    
> 2NN doesn't start with fs.defaultFS set to a viewfs URI unless service RPC address is also set
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3465
>                 URL: https://issues.apache.org/jira/browse/HDFS-3465
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: federation, name-node
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>              Labels: newbie
>
> Looks like the 2NN first tries servicerpc-address then falls back on fs.defaultFS, which won't work in the case of federation since fs.defaultFS doesn't refer to an RPC address. Instead, the 2NN should first check servicerpc-address, then rpc-address, then fall back on fs.defaultFS.
> {noformat}
> Exception in thread "main" java.lang.IllegalArgumentException: Invalid
> URI for NameNode address (check fs.defaultFS): viewfs:/// has no
> authority.
>        at org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:315)
>        at org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:303)
>        at org.apache.hadoop.hdfs.server.namenode.NameNode.getServiceAddress(NameNode.java:296)
>        at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:214)
>        at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.<init>(SecondaryNameNode.java:178)
>        at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.main(SecondaryNameNode.java:582)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira