HDFS candidates for back-porting to Hadoop 2.6.1. The first two were requested in [1].
HADOOP-11674. oneByteBuf in CryptoInputStream and CryptoOutputStream should be non static HADOOP-11710. Make CryptoOutputStream behave like DFSOutputStream wrt synchronization HDFS-7009. Active NN and standby NN have different live nodes. HDFS-7035. Make adding a new data directory to the DataNode an atomic and improve error handling HDFS-7425. NameNode block deletion logging uses incorrect appender. HDFS-7443. Datanode upgrade to BLOCKID_BASED_LAYOUT fails if duplicate block files are present in the same volume. HDFS-7489. Incorrect locking in FsVolumeList#checkDirs can hang datanodes HDFS-7503. Namenode restart after large deletions can cause slow processReport. HDFS-7575. Upgrade should generate a unique storage ID for each volume. HDFS-7579. Improve log reporting during block report rpc failure. HDFS-7587. Edit log corruption can happen if append fails with a quota violation. HDFS-7596. NameNode should prune dead storages from storageMap. HDFS-7611. deleteSnapshot and delete of a file can leave orphaned blocks in the blocksMap on NameNode restart. HDFS-7714. Simultaneous restart of HA NameNodes and DataNode can cause DataNode to register successfully with only one NameNode. HDFS-7733. NFS: readdir/readdirplus return null directory attribute on failure. HDFS-7831. Fix the starting index and end condition of the loop in FileDiffList.findEarlierSnapshotBlocks(). HDFS-7885. Datanode should not trust the generation stamp provided by client. HDFS-7960. The full block report should prune zombie storages even if they're not empty. HDFS-8072. Reserved RBW space is not released if client terminates while writing block. HDFS-8127. NameNode Failover during HA upgrade can cause DataNode to finalize upgrade. Arpit [1] Will Hadoop 2.6.1 be released soon? http://markmail.org/thread/zlsr6prejyogdyvh On 4/27/15, 11:47 AM, "Vinod Kumar Vavilapalli" <vino...@apache.org> wrote: >There were several requests on the user lists [1] for a 2.6.1 release. I >got many offline comments too. > >Planning to do a 2.6.1 release in a few weeks time. We already have a bunch >of tickets committed to 2.7.1. I created a filter [2] to tracking pending >tickets. > >We need to collectively come up with a list of critical issues. We can use >the JIRA Target Version field for the same. I see some but not a whole lot >of new work for this release, most of it is likely going to be pulling in >critical patches from 2.7.1/2.8 etc. > >Thoughts? > >Thanks >+Vinod > >[1] Will Hadoop 2.6.1 be released soon? >http://markmail.org/thread/zlsr6prejyogdyvh >[2] 2.6.1 pending tickets >https://issues.apache.org/jira/issues/?filter=12331711 >
