[
https://issues.apache.org/jira/browse/HDFS-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489696#comment-13489696
]
Kihwal Lee commented on HDFS-4114:
----------------------------------
If a piece of code is not actively maintained and is redundant to or superseded
by a better maintained one, I think deprecating and eventually removing it is
definitely an option. I believe this is what some people feel about BackupNode.
If someone starts contributing changes that are beneficial and meaningful to
the community, the situation can change. But it hasn't happened for quite some
time.
bq. I accept your criticism that BackupNode code path was getting less
attention from me personally and the community at large. Will have to work on
that on my side.
I hope you do and great features and improvements to come out in the future.
Then we will be able to reset "its-getting-old-lets-get-rid-of-it" timer on
BackupNode. How about start deprecating it in 2.0? If any new development based
on BackupNode results in unique features before next major release, we will
un-deprecate it.
> Remove the CheckpointNode
> -------------------------
>
> Key: HDFS-4114
> URL: https://issues.apache.org/jira/browse/HDFS-4114
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Eli Collins
> Assignee: Eli Collins
>
> Per the thread on hdfs-dev@ (http://s.apache.org/tMT) let's remove the
> BackupNode and CheckpointNode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
