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 Wed, 10 Aug 2011 18:52:27 GMT

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

Suresh Srinivas commented on HDFS-2231:
---------------------------------------

bq. I think the general sentiment I'm left with (and I think Rajiv is sort of alluding to)
is that based upon this configuration information, the architecture isn't operationally sound
and/or we're trying to do too much without a real understanding of how this works in practice.
I am not sure if you and Rajiv are talking about the same thing! Rajiv is providing feedback
on why using hostnames to make specific keys is not such a good idea.

> It makes no sense to use a failover IP and have the clients know where the failover IP
might fail over. Especially keep in mind HDFS-34: what will end up happening is that ops teams
will end up having to eat up 5 addresses for 2 HA-NNs. (1 for the failover, 2 for each logical
node, 2 for reach physical node) 
This is not the question about clients. You could use failover address for active and standby
and just use that from client. This could also apply to datanodes. This might be the solution
that some folks go with.

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.

> 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

        

Mime
View raw message