Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 11 Aug 2011 00:53:27 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <880249976.26236.1313024007339.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=13082822#comment-13082822 ] 

Allen Wittenauer commented on HDFS-2231:
----------------------------------------

I don't think I took it out of context. You specifically said:

bq. That second scheme is not to use failover. In such a case, clients need to know about where the active is running. Datanodes needs to know about where both active and standby is running.

I read this as "something which is not failover has an active and a standby that a client cares about"....which makes no sense.    If a client cares about the active server, it is using a failover architecture, no matter how it is painted.

> 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