Re: [Continued] [Release thread] 2.8.0 release activities

* Andrew Wang <andrew.w...@cloudera.com> >> *Sent:* Friday, January 20, 2017 10:48 AM >> *To:* Junping Du >> *Cc:* common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; >> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org >> >> *Subject:*

Re: [Continued] [Release thread] 2.8.0 release activities

___ > From: Andrew Wang <andrew.w...@cloudera.com> > Sent: Friday, January 20, 2017 10:48 AM > To: Junping Du > Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org > Subject: Re: [Continued] [

Re: [Continued] [Release thread] 2.8.0 release activities

cloudera.com> > *Sent:* Friday, January 20, 2017 10:48 AM > *To:* Junping Du > *Cc:* common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org > > *Subject:* Re: [Continued] [Release thread] 2.8.0 release activities >

Re: [Continued] [Release thread] 2.8.0 release activities

:48 AM To: Junping Du Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: [Continued] [Release thread] 2.8.0 release activities You can check the error message by clicking on it, a bunch like this: Missing Sig

Re: [Continued] [Release thread] 2.8.0 release activities

works.com> > Sent: Thursday, January 19, 2017 6:46 PM > To: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org > Cc: Varun Vasudev > Subject: Re: [Continued] [Release thread] 2.8.0 release activities > > According to

Re: [Continued] [Release thread] 2.8.0 release activities

udev Subject: Re: [Continued] [Release thread] 2.8.0 release activities According to Varun's offline email, the security fixes has landed on branch-2, 2.8 and 2.8.0 branch. I was kicking off a new RC build (RC1), and will publish it for vote soon. In the mean time, please mark fix version as 2.8.1 for

Re: [Continued] [Release thread] 2.8.0 release activities

; yarn-...@hadoop.apache.org Cc: Varun Vasudev Subject: Re: [Continued] [Release thread] 2.8.0 release activities Hi folks, In the passed one or two weeks, we found some new blockers get coming on branch-2.8, like: YARN-6068 (log aggregation get stuck when NM restart with work preserving enabled) and YARN-60

Re: [Continued] [Release thread] 2.8.0 release activities

he.org Subject: Re: [Continued] [Release thread] 2.8.0 release activities Hi all Hadoopers, I just commit YARN-3866 which is the last blocker for branch-2.8, so since tomorrow I will kick off process to prepare the first RC for our 2.8.0 release. This release will include at least 2374 c

Re: [Continued] [Release thread] 2.8.0 release activities

tinued] [Release thread] 2.8.0 release activities Thanks Akira for reporting this. Actually, HADOOP-2.8-JACC worked well for several runs before last weekend, but it get failed for latest several runs, probably affected by recently Jenkins down. However, from my recent manual kick off, it seems to be good

Re: [Continued] [Release thread] 2.8.0 release activities

; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: [Continued] [Release thread] 2.8.0 release activities Thanks Junping and Andrew! HADOOP-2.8-JACC is not working well, so I manually kicked a job to compare 2.8 with 2.7.3. https://builds.apac

Re: [Continued] [Release thread] 2.8.0 release activities

ct: Re: [Continued] [Release thread] 2.8.0 release activities I recommend giving the JACC report another look. I set up a parameterized jenkins job which you can trigger manually for branch-2.8: https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/ On Wed, Nov 30, 2016 at 4:06 PM, J

Re: [Continued] [Release thread] 2.8.0 release activities

vilapalli; Jian He; Wangda Tan; > sj...@twitter.com > > *Subject:* Re: [Continued] [Release thread] 2.8.0 release activities > > I recommend giving the JACC report another look. I set up a parameterized > jenkins job which you can trigger manually for branch-2.8: > > https://buil

Re: [Continued] [Release thread] 2.8.0 release activities

ubject: Re: [Continued] [Release thread] 2.8.0 release activities I recommend giving the JACC report another look. I set up a parameterized jenkins job which you can trigger manually for branch-2.8: https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/ On Wed, Nov 30, 2016 at 4

Re: [Continued] [Release thread] 2.8.0 release activities

.@apache.org> > Sent: Wednesday, November 30, 2016 3:24 PM > To: Junping Du > Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod > Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com > Subject:

Re: [Continued] [Release thread] 2.8.0 release activities

u Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com Subject: Re: [Continued] [Release thread] 2.8.0 release activities Thanks for picking this up Junping! I heard on e

Re: [Continued] [Release thread] 2.8.0 release activities

s, > > Junping > > > From: Vinod Kumar Vavilapalli <vino...@apache.org> > Sent: Monday, July 25, 2016 2:57 PM > To: Jian He > Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; > hdfs-...@hadoop.apache.org; commo

[Continued] [Release thread] 2.8.0 release activities

; yarn-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; common-dev@hadoop.apache.org Subject: Re: [Release thread] 2.8.0 release activities Thanks for all that great help moving this release forward, Jian, Sangjin, Wangda et al! Appreciate it. The License / Notice fix is finally in. And I pushed out a

Re: [Release thread] 2.8.0 release activities

Thanks for all that great help moving this release forward, Jian, Sangjin, Wangda et al! Appreciate it. The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last week. I only see 9 blocker / critical fixes pending for 2.8.0 -

RE: [Release thread] 2.8.0 release activities

: Re: [Release thread] 2.8.0 release activities For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs attention for 2.8 MAPREDUCE-6288 YARN-1815 YARN-4685 YARN-4844 The rest are either improvements or long-standing issues and does not qualify release blocker, IMO. I think we’ll try to

Re: [Release thread] 2.8.0 release activities

For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs attention for 2.8 MAPREDUCE-6288 YARN-1815 YARN-4685 YARN-4844 The rest are either improvements or long-standing issues and does not qualify release blocker, IMO. I think we’ll try to get these 4 jiras in asap. The rest will be

Re: [Release thread] 2.8.0 release activities

I see the following list of JIRAs from HADOOP and HDFS as blockers for 2.8.0. Other JIRAs are either old issues with little movement or new issues that don't appear to be as critical/ready. - HADOOP-12893 - HADOOP-12892 - HADOOP-10940 (patch ready?) - HADOOP-12971 (can be done relatively

Re: [Release thread] 2.8.0 release activities

Sounds good to me :). Jian and I have looked at all existing 2.8.0 blockers and criticals today. To me more than half of MR/YARN blockers/criticals of 2.8 should be moved out. Left comments on these JIRAs asked original owners, plan to update target version of these JIRAs early next week. Will

Re: [Release thread] 2.8.0 release activities

How about this? I'll review the HADOOP/HDFS bugs in that list to come up with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll report the list here. Then folks can chime in if you agree Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan? Thanks, Sangjin On

Re: [Release thread] 2.8.0 release activities

+1, we should close such staled JIRAs to avoid doing unnecessary checks for every releases. I'm working on reviewing YARN/MR critical/blocker patches currently, it gonna very helpful if someone else can help with reviewing Common/HDFS JIRAs. Thanks, Wangda On Wed, May 11, 2016 at 4:20 PM,

Re: [Release thread] 2.8.0 release activities

Where do we stand in terms of closing out blocker/critical issues for 2.8.0? I still see 50 open JIRAs in Vinod's list: https://issues.apache.org/jira/issues/?filter=12334985 But I see a lot of JIRAs with no patches or very stale patches. It would be a good exercise to come up with the list of

Re: [Release thread] 2.8.0 release activities

> On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli wrote: > > We are not converging - there’s still 58 more. I need help from the community > in addressing / review 2.8.0 blockers. If folks can start with reviewing > Patch available tickets, that’ll be great. > > I'm

Re: [Release thread] 2.8.0 release activities

We are not converging - there’s still 58 more. I need help from the community in addressing / review 2.8.0 blockers. If folks can start with reviewing Patch available tickets, that’ll be great. Thanks +Vinod > On Apr 4, 2016, at 2:16 PM, Vinod Kumar Vavilapalli > wrote:

Re: [Release thread] 2.8.0 release activities

> On 4 Apr 2016, at 22:16, Vinod Kumar Vavilapalli wrote: > > Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 > now! : https://issues.apache.org/jira/issues/?filter=12334985 > > Also, the docs target (mvn package -Pdocs -DskipTests) is

Re: [Release thread] 2.8.0 release activities

> Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted on branch-2, I figured I have to backport a whole bunch of patches that are only on trunk, and may be more fixes on top of that *sigh* To fix this failure, HADOOP-12022 should be backported to branch-2 and

Re: [Release thread] 2.8.0 release activities

Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 now! : https://issues.apache.org/jira/issues/?filter=12334985 Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted on branch-2, I figured I have to backport a whole bunch of patches that are

Re: [Release thread] 2.8.0 release activities

Sure. The last time I checked, there were 20 odd blocker/critical tickets too that’ll need some of my time. Given that, if you can get them in before a week, we should be good. +Vinod > On Feb 5, 2016, at 1:19 PM, Subramaniam V K wrote: > > Vinod, > > Thanks for

Re: [Release thread] 2.8.0 release activities

Vinod, Thanks for initiating the 2.8 release thread. We are in late review stages for YARN-4420 (Add REST API for listing reservations) and YARN-2575 (Adding ACLs for reservation system), hoping to get them by next week. Any chance you can put off cutting 2.8 by a week as we are planning to

Re: [Release thread] 2.8.0 release activities

> On 3 Feb 2016, at 23:53, Vinod Kumar Vavilapalli wrote: > > Seems like all the features listed in the Roadmap wiki are in. I’m going to > try cutting an RC this weekend for a first/non-stable release off of > branch-2.8. > > Let me know if anyone has any

Re: [Release thread] 2.8.0 release activities

FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0 release. --Chris Nauroth On 2/3/16, 6:19 PM, "Karthik Kambatla" wrote: >Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me. >Let us not call it alpha or beta though, it is

Re: [Release thread] 2.8.0 release activities

Thanks Vinod. +1 for 2.8 release start. Regards, Uma On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" wrote: >Seems like all the features listed in the Roadmap wiki are in. I¹m going >to try cutting an RC this weekend for a first/non-stable release off of >branch-2.8. > >Let

Re: [Release thread] 2.8.0 release activities

Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me. Let us not call it alpha or beta though, it is quite confusing. :) On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma wrote: > Thanks Vinod. +1 for 2.8 release start. > > Regards, > Uma > > On

Re: [Release thread] 2.8.0 release activities

Seems like all the features listed in the Roadmap wiki are in. I’m going to try cutting an RC this weekend for a first/non-stable release off of branch-2.8. Let me know if anyone has any objections/concerns. Thanks +Vinod > On Nov 25, 2015, at 5:59 PM, Vinod Kumar Vavilapalli

[Release thread] 2.8.0 release activities

Forking threads now in order to track all things related to the release. Creating the branch now. Thanks +Vinod > On Nov 25, 2015, at 11:37 AM, Vinod Kumar Vavilapalli > wrote: > > I think we’ve converged at a high level w.r.t 2.8. And as I just sent out an > email, I

Re: [Release thread] 2.8.0 release activities

Branch-2.8 is created. As mentioned before, the goal on branch-2.8 is to put improvements / fixes to existing features with a goal of converging on an alpha release soon. Thanks +Vinod > On Nov 25, 2015, at 5:30 PM, Vinod Kumar Vavilapalli > wrote: > > Forking threads