+1 for removing Checkpoint Node and Backup node -----Original Message----- From: Chris Nauroth [mailto:cnaur...@hortonworks.com] Sent: 06 December 2013 06:27 To: hdfs-dev@hadoop.apache.org Subject: Re: Deprecate BackupNode
+1 Chris Nauroth Hortonworks http://hortonworks.com/ On Thu, Dec 5, 2013 at 4:20 PM, Colin McCabe <cmcc...@alumni.cmu.edu> wrote: > +1 > > Colin > On Dec 4, 2013 3:07 PM, "Suresh Srinivas" <sur...@hortonworks.com> wrote: > > > It is almost an year a jira proposed deprecating backup node - > > https://issues.apache.org/jira/browse/HDFS-4114. > > > > Maintaining it adds unnecessary work. As an example, when I added > > support for retry cache there were bunch of code paths related to > > backup node > that > > added unnecessary work. I do not know of anyone who is using this. > > > > If there are no objections, I want to deprecate that code in 2.3 > > release and remove it from trunk. I will start this work next week. > > > > Regards, > > > > Suresh > > > > > > -- > > http://hortonworks.com/download/ > > > > -- > > 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. > > > -- 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.
