[
https://issues.apache.org/jira/browse/HDFS-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531745#comment-14531745
]
Jesse Yates commented on HDFS-6440:
-----------------------------------
And finally, after working through the comments...
{quote}
The changes to BlockTokenSecretManager - they look fine to me in general, but
I'd love to see some extra tests of this functionality with several NNs in
play. Unless I missed something, I don't think there are any tests that would
exercise more than 2 {{BlockTokenSecretManager}}s
{quote}
There is {{TestFailoverWithBlockTokensEnabled}} which does ensure that multiple
{{BlockTokenSecretManager}}s don't have overlapping ranges, among other
standard blocktoken things - its modified to run with 3NNs.
Looking at the other references to the {{BlockTokenSecretManager}} in tests, it
doesn't seem to be anywhere else we care about testing when there are multiple
NN, just that that the basic range functionality works (which is the main thing
that is being modified). Happy to add more, just not sure what exactly you want
there.
> 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)
