Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BEBF118459 for ; Wed, 13 May 2015 05:40:03 +0000 (UTC) Received: (qmail 60543 invoked by uid 500); 13 May 2015 05:40:01 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 60187 invoked by uid 500); 13 May 2015 05:40:01 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 60138 invoked by uid 99); 13 May 2015 05:40:00 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 May 2015 05:40:00 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 75EC2C1241; Wed, 13 May 2015 05:40:00 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.991 X-Spam-Level: X-Spam-Status: No, score=0.991 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id EqjHZZpMKX7V; Wed, 13 May 2015 05:39:49 +0000 (UTC) Received: from oss.nttdata.co.jp (oss.nttdata.co.jp [49.212.34.109]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id D640224980; Wed, 13 May 2015 05:39:48 +0000 (UTC) Received: from macaa.local (KD106150106098.au-net.ne.jp [106.150.106.98]) by oss.nttdata.co.jp (Postfix) with ESMTP id 0875E17EE35; Wed, 13 May 2015 14:39:02 +0900 (JST) Message-ID: <5552E33F.8040502@oss.nttdata.co.jp> Date: Wed, 13 May 2015 14:38:07 +0900 From: Akira AJISAKA User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: common-dev@hadoop.apache.org, "mapreduce-dev@hadoop.apache.org" , "yarn-dev@hadoop.apache.org" , "hdfs-dev@hadoop.apache.org" Subject: Re: Planning Hadoop 2.6.1 release References: , <8AD4EE147886274A8B495D6AF407DF698124E8DA@szxeml510-mbx.china.huawei.com> In-Reply-To: <8AD4EE147886274A8B495D6AF407DF698124E8DA@szxeml510-mbx.china.huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.7 at oss.nttdata.co.jp X-Virus-Status: Clean Thanks all for collecting jiras for 2.6.1 release. In addition, I'd like to include the following: * HADOOP-11343. Overflow is not properly handled in calculating final iv for AES CTR * YARN-2874. Dead lock in "DelegationTokenRenewer" which blocks RM to execute any further apps * YARN-2992. ZKRMStateStore crashes due to session expiry * YARN-3013. AMRMClientImpl does not update AMRM token properly * YARN-3369. Missing NullPointer check in AppSchedulingInfo causes RM to die * MAPREDUCE-6303. Read timeout when retrying a fetch error can be fatal to a reducer All of these are marked as blocker bug for 2.7.0 but not fixed in 2.6.0. Regards, Akira On 5/4/15 11:15, Brahma Reddy Battula wrote: > Hello Vinod, > > I am thinking,can we include HADOOP-11491 also..? wihout this jira harfs will not be usable when cluster installed in HA mode and try to get filecontext like below.. > > > Path path = new Path("har:///archivedLogs/application_1428917727658_0005-application_1428917727658_0008-1428927448352.har"); > FileSystem fs = path.getFileSystem(new Configuration()); > path = fs.makeQualified(path); > FileContext fc = FileContext.getFileContext(path.toUri(),new Configuration()); > > > > Thanks & Regards > Brahma Reddy Battula > ________________________________________ > From: Chris Nauroth [cnauroth@hortonworks.com] > Sent: Friday, May 01, 2015 4:32 AM > To: mapreduce-dev@hadoop.apache.org; common-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org > Subject: Re: Planning Hadoop 2.6.1 release > > Thank you, Arpit. In addition, I suggest we include the following: > > HADOOP-11333. Fix deadlock in DomainSocketWatcher when the notification > pipe is full > HADOOP-11604. Prevent ConcurrentModificationException while closing domain > sockets during shutdown of DomainSocketWatcher thread. > HADOOP-11648. Set DomainSocketWatcher thread name explicitly > HADOOP-11802. DomainSocketWatcher thread terminates sometimes after there > is an I/O error during requestShortCircuitShm > > HADOOP-11604 and 11648 are not critical by themselves, but they are > pre-requisites to getting a clean cherry-pick of 11802, which we believe > finally fixes the root cause of this issue. > > > --Chris Nauroth > > > > > On 4/30/15, 3:55 PM, "Arpit Agarwal" wrote: > >> 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" >> 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 >>> >> >> >