[
https://issues.apache.org/jira/browse/HDFS-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481709#comment-14481709
]
Jesse Yates commented on HDFS-6440:
-----------------------------------
Us too. We are waiting on a committer to have time to look at it. Head from Lei
that he is happy with the state and had passed it onto [~atm] for review and
commit, but that's the last I head about any progress (that was mid february).
[~patrickwhite] maybe you can get one of the FB commiters to help get it
committed? I'm just tentative to do _another_ rebase of this patch to not have
it be committed.
Honestly, I'm surprised that the various companies that have a stake in HDFS
being successful in production haven't been more supportive of getting this
patch committed.
> Support more than 2 NameNodes
> -----------------------------
>
> Key: HDFS-6440
> URL: https://issues.apache.org/jira/browse/HDFS-6440
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: auto-failover, ha, namenode
> Affects Versions: 2.4.0
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Attachments: Multiple-Standby-NameNodes_V1.pdf,
> hdfs-6440-cdh-4.5-full.patch, hdfs-6440-trunk-v1.patch,
> hdfs-6440-trunk-v1.patch, hdfs-multiple-snn-trunk-v0.patch
>
>
> Most of the work is already done to support more than 2 NameNodes (one
> active, one standby). This would be the last bit to support running multiple
> _standby_ NameNodes; one of the standbys should be available for fail-over.
> Mostly, this is a matter of updating how we parse configurations, some
> complexity around managing the checkpointing, and updating a whole lot of
> tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
