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 Tue, 16 Aug 2011 21:06:27 GMT

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

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

bq. I've asked this many times. It seems that you are building a universal HA framework that
would fit multiple approaches.
I have answered it many times :-) The requirements considered were:
# Non shared vs shared approach
# IP failover vs no IP failover

These multiple approaches are considered because, some folks (working on this jira) want a
solution with no special hardware, no IP failover, and want to use the shared state approach.
Your preference and few other jira posts indicate preference to use BackupNode and possibly
IP failover.

bq. If so that would be "trying to do too much" as Allen states. E.g. with IP failover approach
you probably don't need any configuration changes.
I see. How do you send block reports from datanodes to two namenodesoun

In the prototype you have:
# Backup node configuration is used as place holder for second namenode, with very confusing
backup node becoming active etc. We have gone over this before.
# All the configuration requirement discussed in this jira, you have moved it to the load
balancer. It is not that you do not have it.

bq. The configuration parameters should be the same for Backup and Standby nodes. As these
are only different roles of the single NodeNode. If some of existing parameters need to be
reasonably renamed I'm for it.
The proposal here keeps backward compatibility for configurations using backup node (not sure
if any one is using it!). Second set of params are added for second namenode. I am okay renaming
backup node configurations to do this, if you are confident it will not affect existing setups.
Please provide a detailed design.


> 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