[ https://issues.apache.org/jira/browse/HDFS-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191696#comment-13191696
]
Aaron T. Myers commented on HDFS-2397:
--------------------------------------
+1, the patch looks good to me.
The only other thing I can think to do is that there are probably a few tests out there which
are annotated "@SuppressWarnings({"deprecation"})" because they use the 2NN, which now no
longer need to be annotated as such. I don't know of an easy way to enumerate those. Do you
know if it's a compiler warning to suppress a type of warning that's not actually present
in a given method or class?
> Undeprecate SecondaryNameNode in 0.22, 0.23
> -------------------------------------------
>
> Key: HDFS-2397
> URL: https://issues.apache.org/jira/browse/HDFS-2397
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Todd Lipcon
> Assignee: Eli Collins
> Attachments: hdfs-2397.txt, hdfs-2397.txt, hdfs-2397.txt
>
>
> I would like to consider un-deprecating the SecondaryNameNode for 0.23, and amending
the documentation to indicate that it is still the most trust-worthy way to run checkpoints,
and while CN/BN may have some advantages, they're not battle hardened as of yet. The test
coverage for the 2NN is far superior to the CheckpointNode or BackupNode, and people have
a lot more production experience. Indicating that it is deprecated before we have expanded
test coverage of the CN/BN won't send the right message to our users. (For comparison, look
at what a mess we got into by prematurely deprecating the "old" MR API before the "new" API
had feature parity and a few versions of bug fixes).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
|