Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sun, 7 Aug 2011 23:24:27 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1271596592.15221.1312759467456.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1592140313.13165.1312584507108.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2231) Configuration changes for HA
 namenode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HDFS-2231:
-----------------------------------

Another thought would be to default dfs.namenode.id to "", and if it's empty, try to discover the ID by iterating through all available dfs.namenode.rpc-address.*, checking if any of those addresses is bindable as a local interface. If exactly 1 such IP is found, we can use that ID. If 0 or more than 1 is found, we would bail out due to indeterminate ID.

My thinking is that right now we can always ship the same configuration to all the hosts in the cluster. Having to add things which differ from machine to machine complicates deployment.

> 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)
>
>
> This jira tracks the changes required for configuring HA setup for namenodes.

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