Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 6 Aug 2011 11:37:27 +0000 (UTC)
From: "Uma Maheswara Rao G (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1175105298.13811.1312630647081.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=13080400#comment-13080400 ] 

Uma Maheswara Rao G commented on HDFS-2231:
-------------------------------------------

{quote}
HA solution uses VIP address
1.System needs to be configured with three sets of addresses, NNVIPAddress, NNAddress1 and NNAddress2.
...
....
3.To discover NNStandbyAddress clients and datanode may try NNAddress1 and NNAddress2 or use mechanism such as Zookeeper.
{quote}

In VIP solution, putting dependancy on actual IPs may not be a good choice. 
 To discover NNStandbyAddress clients and datanodes need to retry for actual stanbynode address. 
What if we put another VIPAddress for NNStandbyAddress also?

for example:
Clients and datanodes use standbyNNVIPAddress as NNStandbyAddress.
 So, clients need not bother about retries to find the actual address.

Please correct me if i understud wrongly.

--thanks

> 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