Konstantin, On Sun, Dec 8, 2013 at 1:06 PM, Konstantin Shvachko <shv.had...@gmail.com>wrote:
> I explained my reasoning in the jira > > https://issues.apache.org/jira/browse/HDFS-4114?focusedCommentId=13841326&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13841326 > Please see reply - https://issues.apache.org/jira/browse/HDFS-4114?focusedCommentId=13841600&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13841600 In summary, there is a lot of unnecessary work we are doing to maintain BackupNode. It is not easy to keep you involved on related issues when working on a feature and requires investment of time from people working on a feature. And would like to ask people to hold off removing BN from trunk just yet. > I see it beneficial for everybody - at least business-wise. > Can you enumerate the benefits? If the only case for it is that it is an example of Namenode extension, perhaps another example could be added that is easy to maintain. I have suggested some alternatives to maintaining BackupNode, possibly in github. That way you can continue to maintain it and other HDFS developers do not have to pay the cost of maintaining it. When the plan for it is clear, or the functionality is compelling, we could add it back and chose to maintain it as a community. Regards, Suresh -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
