hadoop-hdfs-issues mailing list archives

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

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

Konstantin Shvachko commented on HDFS-2231:

bq. 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 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.
In my prototype HDFS-2064 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.

> 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