[jira] [Resolved] (HDFS-3013) HA: NameNode format doesn't pick up dfs.namenode.name.dir.NameServiceId configure

["Todd Lipcon (Resolved) (JIRA)" <ji...@apache.org>]

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

Todd Lipcon resolved HDFS-3013.
-------------------------------

       Resolution: Fixed
    Fix Version/s: HA branch (HDFS-1623)
     Hadoop Flags: Reviewed

Ran the tests, no new failures introduced. I also double checked that the new test case fails if the fix is removed. Committed to HA branch. Thanks, Mingjie!
                
> HA: NameNode format doesn't pick up dfs.namenode.name.dir.NameServiceId configure
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-3013
>                 URL: https://issues.apache.org/jira/browse/HDFS-3013
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Mingjie Lai
>            Assignee: Mingjie Lai
>             Fix For: HA branch (HDFS-1623)
>
>         Attachments: HDFS-3013.patch
>
>
> One problem I observed at HA branch is that namenode -format doesn't pick up the right configured dfs.namenode.name.dir.NameServiceId. In this case, ``namenode -format'' will format the default directory instead of the configured one, while namenode will use the correct one. 
> The root cause is that NameNode.initializeGenericKeys() is only invoked at the NameNode constructor. So it doesn't get called by static methods like format and finalize. 

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