hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1914) Federation: namenode storage directory must be configurable specific to a namenode
Date Tue, 17 May 2011 00:40:47 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034457#comment-13034457
] 

Jitendra Nath Pandey commented on HDFS-1914:
--------------------------------------------

+1 for the patch.
Minor: Does it make sense to change DFSUtil.setGenericConf to take a String array as input
instead of String... ? However, it can be addressed in a different jira.

> 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.1.patch, 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

Mime
View raw message