Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 3 Feb 2012 19:51:53 +0000 (UTC)
From: "Todd Lipcon (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <2024708560.8712.1328298713959.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2090465816.54833.1326940119755.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2808) HA: haadmin should use namenode ids
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HDFS-2808:
-----------------------------------

- I think we do have to push the idea of the "nameservice" parameter up into DFSHAAdmin - it doesn't make sense in the context of mapreduce, for example
- In several places you use the term "namespace" where it should be "nameservice"
                
> HA: haadmin should use namenode ids
> -----------------------------------
>
>                 Key: HDFS-2808
>                 URL: https://issues.apache.org/jira/browse/HDFS-2808
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: hdfs-2808.txt, hdfs-2808.txt
>
>
> Currently haadmin services are specified by host:ipcport, we should use a logical names instead, eg dfs.ha.namenode.id when the service is a namenode.

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