[
https://issues.apache.org/jira/browse/HDFS-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Yates updated HDFS-6440:
------------------------------
Attachment: hdfs-6440-trunk-v4.patch
Attaching updated patch. Working through some local test failures - seem like
they might be just due to rebase changes? Looking into it.
Changes of note:
* fixing concurrent checkpoint management - was breaking TestRollingUpgrade -
to not keep around completed checkpoints
* Adding tests to TestRollingUpgrade
Removing random seed setting in testpipelinesfailover
* Fixing startup option setting in minidfscluster#restartNode
* Fixing block manager to use correct nnid lookup
FYI, on vacation through memorial day, so not going to be doing much for the
next few days. Back on Tuesday.
> 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
> Fix For: 3.0.0
>
> Attachments: Multiple-Standby-NameNodes_V1.pdf,
> hdfs-6440-cdh-4.5-full.patch, hdfs-6440-trunk-v1.patch,
> hdfs-6440-trunk-v1.patch, hdfs-6440-trunk-v3.patch, hdfs-6440-trunk-v4.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)
