[jira] [Resolved] (HDFS-2397) Undeprecate SecondaryNameNode

["Eli Collins (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eli Collins resolved HDFS-2397.
-------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

I've committed this and merged to 23. Thanks for the review ATM.
                
> Undeprecate SecondaryNameNode
> -----------------------------
>
>                 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, 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