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 "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2011/05/16 22:22:47 UTC

[jira] [Updated] (HDFS-1914) Federation: namenode storage directory must be configurable specific to a namenode

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

Suresh Srinivas updated HDFS-1914:
----------------------------------

    Attachment: HDFS-1914.patch

Changes:
# While merging federation, TestDFSUtil.java changes was missed. I have added it back. In this patch, I have mostly modified testConfModification() method from that test.
# The patch makes all the namenode and secondary namenode dir keys nameservice specific.

> Federation: namenode storage directory must be configurable specific to a namenode
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-1914
>                 URL: https://issues.apache.org/jira/browse/HDFS-1914
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 0.23.0
>
>         Attachments: HDFS-1914.patch
>
>
> Federation allows common configuration where namenode specific configuration are in the same configuration suffixed by nameservice ID. When namenodes use an external storage directory (NFS), in order to make namenodes use different directories on the external server, the storage directory configuration must also allow specific configuration, using nameservice ID.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira