hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2231) Configuration changes for HA namenode
Date Thu, 06 Oct 2011 07:32:31 GMT

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

Suresh Srinivas updated HDFS-2231:
----------------------------------

    Attachment: HDFS-2231.txt

bq. Why remove DFSUtil.getNameServiceIdKey
With federation there was only one suffix possible to key. With HA, it is combination of service
ID and namenode Id. With that, just getNameServiceIdKey no longer makes sense. Hence the method
is removed.

bq. as not all users will know who "Suresh" is.
With log messages like that, that was exactly the problem I was trying to address :-)
                
> Configuration changes for HA namenode
> -------------------------------------
>
>                 Key: HDFS-2231
>                 URL: https://issues.apache.org/jira/browse/HDFS-2231
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: HA branch (HDFS-1623)
>
>         Attachments: HDFS-2231.txt, HDFS-2231.txt
>
>
> This jira tracks the changes required for configuring HA setup for namenodes.

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