Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8D779200CCB for ; Thu, 20 Jul 2017 21:07:54 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8B91016BEA3; Thu, 20 Jul 2017 19:07:54 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5C3A116BEA1 for ; Thu, 20 Jul 2017 21:07:53 +0200 (CEST) Received: (qmail 23021 invoked by uid 500); 20 Jul 2017 19:07:51 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 22978 invoked by uid 99); 20 Jul 2017 19:07:51 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jul 2017 19:07:51 +0000 Received: from [10.22.9.120] (unknown [192.175.27.10]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C3BB61A0029; Thu, 20 Jul 2017 19:07:50 +0000 (UTC) From: Vinod Kumar Vavilapalli Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_D95C5480-CFAA-498B-893F-3A6B575C7293" Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: About 2.7.4 Release Date: Thu, 20 Jul 2017 12:07:50 -0700 In-Reply-To: Cc: "common-dev@hadoop.apache.org" , Hdfs-dev , "mapreduce-dev@hadoop.apache.org" , "yarn-dev@hadoop.apache.org" To: Konstantin Shvachko References: <8AD4EE147886274A8B495D6AF407DF698F25D8BE@blreml510-mbx.china.huawei.com> <978436dc-9a0c-1072-5092-bb62ec4a69f6@apache.org> X-Mailer: Apple Mail (2.3273) archived-at: Thu, 20 Jul 2017 19:07:54 -0000 --Apple-Mail=_D95C5480-CFAA-498B-893F-3A6B575C7293 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Thanks for taking 2.7.4 over Konstantin! Regarding rolling RC next week, I still see that there are 4 blocker / = critical tickets targeted for 2.7.4: = https://issues.apache.org/jira/issues/?jql=3Dproject%20in%20(HDFS%2C%20MAP= REDUCE%2C%20HADOOP%2C%20YARN)%20AND%20priority%20in%20(Blocker%2C%20Critic= al)%20AND%20resolution%20%3D%20Unresolved%20AND%20%22Target%20Version%2Fs%= 22%20%3D%202.7.4 = . We should get closure on them. = https://issues.apache.org/jira/browse/HDFS-11742 = definitely was = something that was deemed a blocker for 2.8.2, not sure about 2.7.4. I=E2=80=99m =E2=80=98back=E2=80=99 - let me know if you need any help. Thanks +Vinod > On Jul 13, 2017, at 5:45 PM, Konstantin Shvachko = wrote: >=20 > Hi everybody. >=20 > We have been doing some internal testing of Hadoop 2.7.4. The testing = is > going well. > Did not find any major issues on our workloads. > Used an internal tool called Dynamometer to check NameNode performance = on > real cluster traces. Good. > Overall test cluster performance looks good. > Some more testing is still going on. >=20 > I plan to build an RC next week. If there are no objection. >=20 > Thanks, > --Konst >=20 > On Thu, Jun 15, 2017 at 4:42 PM, Konstantin Shvachko = > wrote: >=20 >> Hey guys. >>=20 >> An update on 2.7.4 progress. >> We are down to 4 blockers. There is some work remaining on those. >> https://issues.apache.org/jira/browse/HDFS-11896?filter=3D12340814 >> Would be good if people could follow up on review comments. >>=20 >> I looked through nightly Jenkins build results for 2.7.4 both on = Apache >> Jenkins and internal. >> Some test fail intermittently, but there no consistent failures. I = filed >> HDFS-11985 to track some of them. >> https://issues.apache.org/jira/browse/HDFS-11985 >> I do not currently consider these failures as blockers. LMK if some = of >> them are. >>=20 >> We started internal testing of branch-2.7 on one of our smallish = (100+ >> nodes) test clusters. >> Will update on the results. >>=20 >> There is a plan to enable BigTop for 2.7.4 testing. >>=20 >> Akira, Brahma thank you for setting up a wiki page for 2.7.4 release. >> Thank you everybody for contributing to this effort. >>=20 >> Regards, >> --Konstantin >>=20 >>=20 >> On Tue, May 30, 2017 at 12:08 AM, Akira Ajisaka >> wrote: >>=20 >>> Sure. >>> If you want to edit the wiki, please tell me your ASF confluence = account. >>>=20 >>> -Akira >>>=20 >>> On 2017/05/30 15:31, Rohith Sharma K S wrote: >>>=20 >>>> Couple of more JIRAs need to be back ported for 2.7.4 release. = These will >>>> solve RM HA unstability issues. >>>> https://issues.apache.org/jira/browse/YARN-5333 >>>> https://issues.apache.org/jira/browse/YARN-5988 >>>> https://issues.apache.org/jira/browse/YARN-6304 >>>>=20 >>>> I will raise a JIRAs to back port it. >>>>=20 >>>> @Akira , could you help to add these JIRAs into wiki? >>>>=20 >>>> Thanks & Regards >>>> Rohith Sharma K S >>>>=20 >>>> On 29 May 2017 at 12:19, Akira Ajisaka wrote: >>>>=20 >>>> Created a page for 2.7.4 release. >>>>> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.7.4 >>>>>=20 >>>>> If you want to edit this wiki, please ping me. >>>>>=20 >>>>> Regards, >>>>> Akira >>>>>=20 >>>>>=20 >>>>> On 2017/05/23 4:42, Brahma Reddy Battula wrote: >>>>>=20 >>>>> Hi Konstantin Shvachko >>>>>>=20 >>>>>>=20 >>>>>> how about creating a wiki page for 2.7.4 release status like 2.8 = and >>>>>> trunk in following link.?? >>>>>>=20 >>>>>>=20 >>>>>> https://cwiki.apache.org/confluence/display/HADOOP >>>>>>=20 >>>>>>=20 >>>>>> ________________________________ >>>>>> From: Konstantin Shvachko >>>>>> Sent: Saturday, May 13, 2017 3:58 AM >>>>>> To: Akira Ajisaka >>>>>> Cc: Hadoop Common; Hdfs-dev; mapreduce-dev@hadoop.apache.org; >>>>>> yarn-dev@hadoop.apache.org >>>>>> Subject: Re: About 2.7.4 Release >>>>>>=20 >>>>>> Latest update on the links and filters. Here is the correct link = for >>>>>> the >>>>>> filter: >>>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa? >>>>>> requestId=3D12340814 >>>>>>=20 >>>>>> Also updated: https://s.apache.org/Dzg4 >>>>>>=20 >>>>>> Had to do some Jira debugging. Sorry for confusion. >>>>>>=20 >>>>>> Thanks, >>>>>> --Konstantin >>>>>>=20 >>>>>> On Wed, May 10, 2017 at 2:30 PM, Konstantin Shvachko < >>>>>> shv.hadoop@gmail.com> >>>>>> wrote: >>>>>>=20 >>>>>> Hey Akira, >>>>>>=20 >>>>>>>=20 >>>>>>> I didn't have private filters. Most probably Jira caches = something. >>>>>>> Your filter is in the right direction, but for some reason it = lists >>>>>>> only >>>>>>> 22 issues, while mine has 29. >>>>>>> It misses e.g. YARN-5543 >>>>>> a/browse/YARN-5543> >>>>>>> . >>>>>>>=20 >>>>>>> Anyways, I created a Jira filter now "Hadoop 2.7.4 release = blockers", >>>>>>> shared it with "everybody", and updated my link to point to that >>>>>>> filter. >>>>>>> So >>>>>>> you can use any of the three methods below to get the correct = list: >>>>>>> 1. Go to https://s.apache.org/Dzg4 >>>>>>> 2. Go to the filter via >>>>>>> https://issues.apache.org/jira/issues?filter=3D12340814 >>>>>>> or by finding "Hadoop 2.7.4 release blockers" filter in the = jira >>>>>>> 3. On Advanced issues search page paste this: >>>>>>> project in (HDFS, HADOOP, YARN, MAPREDUCE) AND labels =3D >>>>>>> release-blocker >>>>>>> AND "Target Version/s" =3D 2.7.4 >>>>>>>=20 >>>>>>> Hope this solves the confusion for which issues are included. >>>>>>> Please LMK if it doesn't, as it is important. >>>>>>>=20 >>>>>>> Thanks, >>>>>>> --Konstantin >>>>>>>=20 >>>>>>> On Tue, May 9, 2017 at 9:58 AM, Akira Ajisaka = >>>>>>> wrote: >>>>>>>=20 >>>>>>> Hi Konstantin, >>>>>>>=20 >>>>>>>>=20 >>>>>>>> Thank you for volunteering as release manager! >>>>>>>>=20 >>>>>>>> Actually the original link works fine: = https://s.apache.org/Dzg4 >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> I couldn't see the link. Maybe is it private filter? >>>>>>>>=20 >>>>>>>> Here is a link I generated: https://s.apache.org/ehKy >>>>>>>> This filter includes resolved issue and excludes fixversion =3D=3D= 2.7.4 >>>>>>>>=20 >>>>>>>> Thanks and Regards, >>>>>>>> Akira >>>>>>>>=20 >>>>>>>> On 2017/05/08 19:20, Konstantin Shvachko wrote: >>>>>>>>=20 >>>>>>>> Hi Brahma Reddy Battula, >>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Actually the original link works fine: = https://s.apache.org/Dzg4 >>>>>>>>> Your link excludes closed and resolved issues, which needs >>>>>>>>> backporting, >>>>>>>>> and >>>>>>>>> which we cannot reopen, as discussed in this thread earlier. >>>>>>>>>=20 >>>>>>>>> Looked through the issues you proposed: >>>>>>>>>=20 >>>>>>>>> HDFS-9311 >>>>>>>>> Seems like a new feature. It helps failover to standby node = when >>>>>>>>> primary >>>>>>>>> is >>>>>>>>> under heavy load, but it introduces new APIs, addresses, = config >>>>>>>>> parameters. >>>>>>>>> And needs at least one follow up jira. >>>>>>>>> Looks like a backward compatible change, though. >>>>>>>>> Did you have a chance to run it in production? >>>>>>>>>=20 >>>>>>>>> +1 on >>>>>>>>> HDFS-10987 >>>>>>>>>=20 >>>>>>>>> [HDFS-10987] Make Decommission less expensive when lot of ...< >>>>>>>>=20 >>>>>>> https://issues.apache.org/jira/browse/HDFS-10987> >>>>>> issues.apache.org >>>>>> When user want to decommission a node which having 50M blocks ,it = could >>>>>> hold the namesystem lock for long time.We've seen it is taking 36 = sec. >>>>>> As >>>>>> we knew during this ... >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> HDFS-9902 >>>>>>=20 >>>>>>>=20 >>>>>>>>> [HDFS-9902] Support different values of dfs.datanode.du ...< >>>>>>>>=20 >>>>>>> https://issues.apache.org/jira/browse/HDFS-9902> >>>>>> issues.apache.org >>>>>> Now Hadoop support different storage type for DISK, SSD, ARCHIVE = and >>>>>> RAM_DISK, but they share one configuration = dfs.datanode.du.reserved. >>>>>> The >>>>>> DISK size may be several ... >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> HDFS-8312 >>>>>>=20 >>>>>>>=20 >>>>>>>>> Trash does not descent into child directories to check for = ...< >>>>>>>>=20 >>>>>>> https://issues.apache.org/jira/browse/HDFS-8312> >>>>>> issues.apache.org >>>>>> HDFS trash does not descent into child directory to check if user = has >>>>>> permission to delete files. For example: Run the following = command to >>>>>> initialize directory ... >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> HADOOP-14100 >>>>>>=20 >>>>>>>=20 >>>>>>>>> Upgrade Jsch jar to latest version to fix vulnerability in = ...< >>>>>>>>=20 >>>>>>> https://issues.apache.org/jira/browse/HADOOP-14100> >>>>>> issues.apache.org >>>>>> Recently there was on vulnerability reported on jsch library. Its = fixed >>>>>> in latest 0.1.54 version before CVE was made public. >>>>>> https://cve.mitre.org/cgi-bin/cvename.cgi ... >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> Added them to 2.7.4 release. You should see them via the above = link >>>>>>>>> now. >>>>>>>>> Would be good if you could attach backport patches for some of = them? >>>>>>>>>=20 >>>>>>>>> Appreciate your help, >>>>>>>>> --Konstantin >>>>>>>>>=20 >>>>>>>>> On Mon, May 8, 2017 at 8:39 AM, Brahma Reddy Battula < >>>>>>>>> brahmareddy.battula@huawei.com> wrote: >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Looks following link is not correct.. >>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> https://s.apache.org/Dzg4 >>>>>>>>>>=20 >>>>>>>>>> It should be like following..? >>>>>>>>>>=20 >>>>>>>>>> https://s.apache.org/wi3U >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Apart from Konstantin mentioned,Following also good to go..? = let me >>>>>>>>>> know >>>>>>>>>> your thoughts on this. >>>>>>>>>>=20 >>>>>>>>>> For Large Cluster: >>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>>>>>>=20 >>>>>>>>>> https://issues.apache.org/jira/browse/HDFS-9311=3D=3D=3DLife = Line >>>>>>>>>> Protocol >>>>>>>>>> = https://issues.apache.org/jira/browse/HDFS-10987=3D=3D=3DDeecommission >>>>>>>>>> Expensive when lot's of blocks are present >>>>>>>>>>=20 >>>>>>>>>> https://issues.apache.org/jira/browse/HDFS-9902=3D=3D=3D >>>>>>>>>> "dfs.datanode.du.reserved" per Storage Type >>>>>>>>>>=20 >>>>>>>>>> For Security: >>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>>>>>> https://issues.apache.org/jira/browse/HDFS-8312=3D=3D=3DTrash = does not >>>>>>>>>> descent >>>>>>>>>> into child directories to check for permission >>>>>>>>>> https://issues.apache.org/jira/browse/HADOOP-14100=3D=3D=3DUpgr= ade Jsch >>>>>>>>>> jar >>>>>>>>>> to >>>>>>>>>> latest version to fix vulnerability in old versions >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Regards >>>>>>>>>> Brahma Reddy Battula >>>>>>>>>>=20 >>>>>>>>>> -----Original Message----- >>>>>>>>>> From: Erik Krogen [mailto:ekrogen@linkedin.com.INVALID] >>>>>>>>>> Sent: 06 May 2017 02:40 >>>>>>>>>> To: Konstantin Shvachko >>>>>>>>>> Cc: Zhe Zhang; Hadoop Common; Hdfs-dev; >>>>>>>>>> mapreduce-dev@hadoop.apache.org >>>>>>>>>> ; >>>>>>>>>> yarn-dev@hadoop.apache.org >>>>>>>>>> Subject: Re: About 2.7.4 Release >>>>>>>>>>=20 >>>>>>>>>> List LGTM Konstantin! >>>>>>>>>>=20 >>>>>>>>>> Let's say that we will only create a new tracking JIRA for = patches >>>>>>>>>> which >>>>>>>>>> do not backport cleanly, to avoid having too many lying = around. >>>>>>>>>> Otherwise >>>>>>>>>> we can directly attach to old ticket. If a clean backport = does >>>>>>>>>> happen >>>>>>>>>> to >>>>>>>>>> break a test the nightly build will help us catch it. >>>>>>>>>>=20 >>>>>>>>>> Erik >>>>>>>>>>=20 >>>>>>>>>> On Thu, May 4, 2017 at 7:21 PM, Konstantin Shvachko < >>>>>>>>>> shv.hadoop@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>> Great Zhe. Let's monitor the build. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>> I marked all jiras I knew of for inclusion into 2.7.4 as I >>>>>>>>>>> described >>>>>>>>>>> before. >>>>>>>>>>> Target Version/s: 2.7.4 >>>>>>>>>>> Label: release-blocker >>>>>>>>>>>=20 >>>>>>>>>>> Here is the link to the list: https://s.apache.org/Dzg4 = Please >>>>>>>>>>> let >>>>>>>>>>> me >>>>>>>>>>> know if I missed anything. >>>>>>>>>>> And feel free to pick up any. Most of backports are pretty >>>>>>>>>>> straightforward, but not all. >>>>>>>>>>>=20 >>>>>>>>>>> We can create tracking jiras for backporting if you need to = run >>>>>>>>>>> Jenkins on the patch (and since Allen does not allow = reopening >>>>>>>>>>> them). >>>>>>>>>>> But I think the final patch should be attached to the = original >>>>>>>>>>> jira. >>>>>>>>>>> Otherwise history will be hard to follow. >>>>>>>>>>>=20 >>>>>>>>>>> Thanks, >>>>>>>>>>> --Konstantin >>>>>>>>>>>=20 >>>>>>>>>>> On Wed, May 3, 2017 at 4:53 PM, Zhe Zhang = wrote: >>>>>>>>>>>=20 >>>>>>>>>>> Thanks for volunteering as RM Konstantin! The plan LGTM. >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>>> I've created a nightly Jenkins job for branch-2.7 (unit = tests): >>>>>>>>>>>> https://builds.apache.org/job/Hadoop-branch2.7-nightly/ >>>>>>>>>>>>=20 >>>>>>>>>>>> On Wed, May 3, 2017 at 12:42 AM Konstantin Shvachko < >>>>>>>>>>>>=20 >>>>>>>>>>>> shv.hadoop@gmail.com> >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> Hey guys, >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>> I and a few of my colleagues would like to help here and = move >>>>>>>>>>>>> 2.7.4 >>>>>>>>>>>>> release forward. A few points in this regard. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> 1. Reading through this thread since March 1 I see that = Vinod >>>>>>>>>>>>> hinted on managing the release. Vinod, if you still want = the >>>>>>>>>>>>> job / >>>>>>>>>>>>> have bandwidth will be happy to work with you. >>>>>>>>>>>>> Otherwise I am glad to volunteer as the release manager. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> 2. In addition to current blockers and criticals, I would = like >>>>>>>>>>>>> to >>>>>>>>>>>>>=20 >>>>>>>>>>>>> propose >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>> a >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> few issues to be included in the release, see the list = below. >>>>>>>>>>>>> Those >>>>>>>>>>>>> are mostly bug fixes and optimizations, which we already = have in >>>>>>>>>>>>> our >>>>>>>>>>>>>=20 >>>>>>>>>>>>> internal >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>> branch and run in production. Plus one minor feature "node >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> labeling", which we found very handy, when you have = heterogeneous >>>>>>>>>>>>> environments and mixed workloads, like MR and Spark. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> 3. For marking issues for the release I propose to >>>>>>>>>>>>> - set the target version to 2.7.4, and >>>>>>>>>>>>> - add a new label "release-blocker" >>>>>>>>>>>>> That way we will know issues targeted for the release = without >>>>>>>>>>>>> reopening them for backports. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> 4. I see quite a few people are interested in the release. = With >>>>>>>>>>>>> all >>>>>>>>>>>>> the help I think we can target to release by the end of = May. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Other things include fixing CHANGES.txt and fixing Jenkins = build >>>>>>>>>>>>> for >>>>>>>>>>>>>=20 >>>>>>>>>>>>> 2.7.4 >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>> branch. >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> --Konstantin >>>>>>>>>>>>>=20 >>>>>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D List of issue for 2.7.4 = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>>>>>>>>> ------ Backports >>>>>>>>>>>>> HADOOP-12975 >>>>>>>>>>>> a/browse/HADOOP-12975>. >>>>>>>>>>>>> Add >>>>>>>>>>>>>=20 >>>>>>>>>>>>> du >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>> jitters >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> HDFS-9710 = . IBR >>>>>>>>>>>>>=20 >>>>>>>>>>>>> batching >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>> HDFS-10715 = . >>>>>>>>>>> NPE >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> when applying AvailableSpaceBlockPlacementPolicy >>>>>>>>>>>>> HDFS-2538 = . >>>>>>>>>>>>> fsck >>>>>>>>>>>>>=20 >>>>>>>>>>>>> removal >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>> of dot printing >>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> HDFS-8131 = . >>>>>>>>>>>>> space-balanced >>>>>>>>>>>>> policy for balancer >>>>>>>>>>>>> HDFS-8549 = . >>>>>>>>>>>>> abort >>>>>>>>>>>>> balancer if upgrade in progress >>>>>>>>>>>>> HDFS-9412 = . >>>>>>>>>>>>> skip >>>>>>>>>>>>> small blocks in getBlocks >>>>>>>>>>>>>=20 >>>>>>>>>>>>> YARN-1471 = . >>>>>>>>>>>>> SLS >>>>>>>>>>>>> simulator >>>>>>>>>>>>> YARN-4302 = . >>>>>>>>>>>>> SLS >>>>>>>>>>>>> YARN-4367 = . >>>>>>>>>>>>> SLS >>>>>>>>>>>>> YARN-4612 = . >>>>>>>>>>>>> SLS >>>>>>>>>>>>>=20 >>>>>>>>>>>>> ----- Node labeling >>>>>>>>>>>>> MAPREDUCE-6304 >>>>>>>>>>>>> >>>>>>>>>>>>> YARN-2943 = >>>>>>>>>>>>> YARN-4109 = >>>>>>>>>>>>> YARN-4140 = >>>>>>>>>>>>> YARN-4250 = >>>>>>>>>>>>> YARN-4925 = >>>>>>>>>>>>>=20 >>>>>>>>>>>>> -- >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Zhe Zhang >>>>>>>>>>>> Apache Hadoop Committer >>>>>>>>>>>> http://zhe-thoughts.github.io/about/ | @oldcap >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>=20 >>>>>> = --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org >>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org >>>>>=20 >>>>>=20 >>>>>=20 >>>>=20 >>=20 --Apple-Mail=_D95C5480-CFAA-498B-893F-3A6B575C7293--