Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 21 May 2012 17:51:41 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <395891868.3996.1337622701495.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1157119170.4632.1328215740626.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2885) Remove "federation" from the
 nameservice config options
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE commented on HDFS-2885:
----------------------------------------------

Eli, thanks for reviewing and committing this!
                
> Remove "federation" from the nameservice config options
> -------------------------------------------------------
>
>                 Key: HDFS-2885
>                 URL: https://issues.apache.org/jira/browse/HDFS-2885
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.23.1
>            Reporter: Eli Collins
>            Assignee: Tsz Wo (Nicholas), SZE
>             Fix For: 2.0.1
>
>         Attachments: h2885_20120518.patch, h2885_20120518b.patch
>
>
> HDFS-1623, and potentially other HDFS features will use the nameservice abstraction, even if federation is not enabled (eg you need to configure {{dfs.federation.nameservices}} in HA even if you're not using federation just to declare your nameservice). This is confusing to users. We should consider deprecating and removing "federation" from the {{dfs.federation.nameservices}} and {{dfs.federation.nameservice.id}} config options, as {{dfs.nameservices}} and {{dfs.nameservice.id}} are more intuitive.

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