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 "Charles Lamb (JIRA)" <ji...@apache.org> on 2014/09/23 04:20:34 UTC

[jira] [Updated] (HDFS-7132) hdfs namenode -metadataVersion command does not honor configured name dirs

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

Charles Lamb updated HDFS-7132:
-------------------------------
    Attachment: HDFS-7132.001.patch

The -metadataVersion subcommand does not actually create a NameNode instance. This means that suffixed config params like DFS_NAMENODE_NAME_DIR_KEY do not get initialized.

This patch causes the -metadataVersion to call NameNode.initializeGenericKeys. It also modifies TestMetadataVersion to cover this case.

> hdfs namenode -metadataVersion command does not honor configured name dirs
> --------------------------------------------------------------------------
>
>                 Key: HDFS-7132
>                 URL: https://issues.apache.org/jira/browse/HDFS-7132
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 2.6.0
>            Reporter: Charles Lamb
>            Assignee: Charles Lamb
>            Priority: Minor
>         Attachments: HDFS-7132.001.patch
>
>
> The hdfs namenode -metadataVersion command does not honor dfs.namenode.name.dir.<nameservice>.<namenode> configuration parameters.



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