[
https://issues.apache.org/jira/browse/HDFS-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated HDFS-6440:
------------------------------
Attachment: Multiple-Standby-NameNodes_V1.pdf
hdfs-multiple-snn-trunk-v0.patch
Attaching a patch on top of trunk (at least as of a couple weeks ago).
Also, attaching a design doc as a guide for anyone who wants to take on
reviewing this one :)
FWIW, we are running this patch in production at Salesforce(1), added
additional unit tests that pass alongside the original unit tests, and did an
extensive load testing under adverse conditions via m/r (see design doc).
(1) well, on top of the latest CDH release :)
> 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-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)
