hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3351) NameNode#initializeGenericKeys should always set fs.defaultFS regardless of whether HA or Federation is enabled
Date Wed, 02 May 2012 21:48:51 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aaron T. Myers updated HDFS-3351:
---------------------------------

    Attachment: HDFS-3351.patch

Here's a patch which addresses the bug. Configuration keys will still only be initialized
if either HA or federation is enabled in the conf, but fs.defaultFS will always be set regardless.
                
> NameNode#initializeGenericKeys should always set fs.defaultFS regardless of whether HA
or Federation is enabled
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3351
>                 URL: https://issues.apache.org/jira/browse/HDFS-3351
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 2.0.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: HDFS-3351.patch
>
>
> NameNode#initializeGenericKeys exits early if neither a nameservice nor NN ID is passed.
However, this method also serves to set fs.defaultFS in the configuration object stored by
the NN to the NN RPC address after generic keys have been configured. This should be done
in all cases.

--
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

        

Mime
View raw message