hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2231) Configuration changes for HA namenode
Date Thu, 11 Aug 2011 06:51:27 GMT

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

Suresh Srinivas commented on HDFS-2231:

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

The context of this is that, the failover in the above statement is ip failover and not failover
of active to standby namenodes.

bq. I think you can say both at this point. Since this jira still talks about VIP and non-VIP,
shared-storage and no-shared-storage solutions, which should be resolved as the implementations
a very different for these approaches.
I am not sure about your conclusion here Konstantin. You want to use backup node approch with
ip failover and a special rejiggered load balancer for dual block reports. Some want solution
where they do not want ip failover, nor special load balancer.

bq. I did not introduce or change a single config key. Not saying it is good, just that it
can be done. And concentrating on one single approach rather than building a universal plugable
HA framework will simplify things.
You are using backup namenode configuration keys. So it is not that you are making changes.
The changes you need are already there. Also I think if you do not make changes. and overload
backup configuration to mean standby, it is not clean. Various discussions have covered this

> 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


View raw message