[RESULT][VOTE] Release Apache Hadoop 2.7.2 RC2

Here’s my +1 to conclude the vote. With 12 binding +1s, 11 non-binding +1s and no -1s, this vote passes. I’ll push forward the release process. Thanks to everyone who voted. +Vinod > On Jan 14, 2016, at 8:57 PM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > >

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

Here’s my +1 to conclude the vote. With 12 binding +1s, 11 non-binding +1s and no -1s, this vote passes. I’ll push forward the release process. Thanks to everyone who voted. +Vinod > On Jan 14, 2016, at 8:57 PM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > >

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

dev@hadoop.apache.org > <mailto:hdfs-dev@hadoop.apache.org>; mapreduce-...@hadoop.apache.org > <mailto:mapreduce-...@hadoop.apache.org>; Vinod Kumar Vavilapalli > Subject: Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale > branches > > Thanks

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

ask them to be locked up? > > Thanks > Karthik > > On Thu, Jan 14, 2016 at 10:26 PM, Vinod Kumar Vavilapalli < > vino...@apache.org> wrote: > >> Hi all, >> >> As some of you have noticed, we have an update from ASF infra on git >> branching

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

ty.reservations-continue-look-all-nodes is on by > default, I think we should fix this. If we decide to ship 2.7.2 without that > fix then the release notes should call out that JIRA and mention the > workaround of setting > yarn.scheduler.capacity.reservations-continue-look-all-nod

[VOTE] Release Apache Hadoop 2.7.2 RC2

Hi all, I've created an updated release candidate RC2 for Apache Hadoop 2.7.2. As discussed before, this is the next maintenance release to follow up 2.7.1. The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/ The RC tag in git is: release-2.7.2-RC2 The

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

It kind of got lost through my email, but when I talked about force-push, it is almost completely in the context of feature-branch rebase. We almost never do force-push outside of this context, neither do we encourage it. And like I pointed, the fact that the mainline branches (trunk, branch-2

[UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

Hi all, As some of you have noticed, we have an update from ASF infra on git branching policy: We no longer have a ASF wide mandate on disallowing force-pushes on all branches / tags. Summarizing information from the INFRA email for the sake of clarity in the midst of recent confusion - We

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

Mailing infra ate all the formatting up. Here’s the same email with some line breaks. > Hi all, > > As some of you have noticed, we have an update from ASF infra on git > branching policy: We no longer have a ASF wide mandate on disallowing > force-pushes on all branches / tags. >

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

anches. Some fixes could be trivial (test case fix, > etc.) enough to deserve more flexibility.​ I would prefer this rule only > applies on critical/blocker fixes, but not applies on minor/trivial issues. > Just 2 cents. > > Thanks, > > Junping > > From: Vinod

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

cordReader,TestMRTimelineEventHandling,TestDistributedShell,TestFileSystemNodeLabelsStore,TestCapacityScheduler @Junping, mind giving a look at the branch for sanity checks? Thanks +Vinod > On Jan 13, 2016, at 11:02 AM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > Thanks for th

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

Sigh. Missed this. To retain causality ("any fix in 2.6.3 will be there in all releases that got out after 2.6.3”), I’ll get these patches in. Reverting my +1, and casting -1 for the RC myself. Will spin a new RC, this voting thread is marked dead. Thanks +Vinod > On Dec 22, 2015, at 8:24

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+Vinod > On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > Sigh. Missed this. > > To retain causality ("any fix in 2.6.3 will be there in all releases that got > out after 2.6.3”), I’ll get these patches in. > > Rever

Re: [Important] Lots of 2.8.0 commits are in branch-2 only

end. > > Thanks, > --Konst > > On Wed, Dec 16, 2015 at 6:52 PM, Vinod Kumar Vavilapalli <vino...@apache.org >> wrote: > >> Not entirely sure we have enough info to warrant a hard-reset. Yet. >> >> Do we know how many of these are new features / im

Re: [Important] Lots of 2.8.0 commits are in branch-2 only

In fact, 3 out of those 4 bugs are part of a bigger umbrella refactor effort. So I don’t see any problem as of now. +Vinod > On Dec 17, 2015, at 11:29 AM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > Wangda, > > I see just 13 tickets *only in 2.9.0* >

Re: [Important] Lots of 2.8.0 commits are in branch-2 only

Wangda, I see just 13 tickets *only in 2.9.0* (https://issues.apache.org/jira/issues/?jql=project%20in%20%28YARN%2C%20MAPREDUCE%2C%20HDFS%2C%20HADOOP%29%20AND%20resolution%20%3D%20Fixed%20and%20fixVersion%20%3D%202.9.0%20ORDER%20BY%20priority%20DESC). If you leave the new features /

Re: [VOTE] Release Apache Hadoop 2.6.3 RC0

So, the original voting mail mentions we are voting on release-2.6.3-RC0 tag. Are we still doing that? What are the RC0.1 and RC1 tags doing then? +Vinod > On Dec 16, 2015, at 2:13 AM, Junping Du wrote: > > Thanks Akira for notice this. I don't think we can remove these

Re: [VOTE] Release Apache Hadoop 2.6.3 RC0

. - Navigated through the MapReduce UI to make sure the views are working well. Thanks, +Vinod > On Dec 16, 2015, at 11:32 AM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > So, the original voting mail mentions we are voting on release-2.6.3-RC0 tag. > > Are w

Re: [VOTE] Release Apache Hadoop 2.7.2 RC0

The last of the blockers went in late last week. Re-spinning the RC now. Thanks +Vinod > On Nov 13, 2015, at 10:26 AM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > Thanks for reporting this Jason! > > Everyone, I am canceling this RC given the feedback

Re: [VOTE] Release Apache Hadoop 2.7.2 RC0

15, 2015, at 12:59 AM, Konstantin Shvachko <shv.had...@gmail.com> > wrote: > > Sorry for bringing this up late. > I think we should pick up HDFS-9516 for this release. > Rather critical bug fix, but up to you, Vinod. > > Thanks, > --Konst > > On Wed, Nov 11, 2

Re: Erasure coding in branch-2 [Was Re: [VOTE] Merge HDFS-7285 (erasure coding) branch to trunk]

Forgot to update this thread. I branched off 2.8 last week. So, we can now go ahead and do a merge of HDFS-7285 into branch-2 (version 2.9) like we discussed before. Thanks +Vinod > On Nov 3, 2015, at 4:40 PM, Vinod Kumar Vavilapalli <vino...@hortonworks.com> > wrote: > >

Re: continuing releases on Apache Hadoop 2.6.x

+1, this sounds good to me. Thanks +Vinod > On Nov 25, 2015, at 11:44 AM, Junping Du wrote: > > May be we should quickly go through landed patches in 2.6.3 list and postpone > any risky patches to 2.6.4? >

Re: [DISCUSS] Looking to a 2.8.0 release

This is the current state from the feedback I gathered. - Support priorities across applications within the same queue YARN-1963 — Can push as an alpha / beta feature per Sunil - YARN-1197 Support changing resources of an allocated container: — Can push as an alpha/beta feature per

[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 <vino...@apache.org> > wrote: > > I think we’ve converged at a high level w.r.t 2.8. And as I just sent

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 <vino...@apache.org> > wrote: > &g

Re: [DISCUSS] Looking to a 2.8.0 release

There are 40 odd incompatible changes in 3.x:

Re: [DISCUSS] Looking to a 2.8.0 release

only (a) the feature-set documented under 2.8 in the RoadMap wiki and (b) other minor features that are already in 2.8. Thanks +Vinod > On Nov 11, 2015, at 12:13 PM, Vinod Kumar Vavilapalli > <vino...@hortonworks.com> wrote: > > - Cut a branch about two weeks from now >

Re: [DISCUSS] Looking to a 2.8.0 release

, this feature is only useful in some very > unique deployment architectures right now. This is all discussed > explicitly in documentation committed with HDFS-8155, but I wanted to > prevent any mistaken assumptions for people only reading this thread. > > --Chris Nauroth > >

Re: [DISCUSS] Looking to a 2.8.0 release

alpha features set their interface stability annotations > to "evolving". There isn't a corresponding annotation for "interface > quality", but IMO that's overkill. > > Thanks, > Andrew > > On Wed, Nov 25, 2015 at 11:08 AM, Vinod Kumar Vavilapalli <

Release votes and git-tags [Was Re: [VOTE] Release Apache Hadoop 2.7.2 RC0]

We have always voted on release tar-balls, not svn branches / git commit-ids or tags. When we were on SVN, we used to paste in the voting thread the release branch URL. Since we moved to git, we stopped creating release branches and have always used signed tags for snapshotting and posted

[VOTE] Release Apache Hadoop 2.7.2 RC0

Hi all, I've created a release candidate RC0 for Apache Hadoop 2.7.2. As discussed before, this is the next maintenance release to follow up 2.7.1. The RC is available for validation at: *http://people.apache.org/~vinodkv/hadoop-2.7.2-RC0/

[jira] [Resolved] (HDFS-7633) BlockPoolSliceScanner fails when Datanode has too many blocks

[ https://issues.apache.org/jira/browse/HDFS-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HDFS-7633. --- Resolution: Not A Problem Fix Version/s: (was: 2.6.1) Resolving

[jira] [Reopened] (HDFS-7633) BlockPoolSliceScanner fails when Datanode has too many blocks

[ https://issues.apache.org/jira/browse/HDFS-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HDFS-7633: --- > BlockPoolSliceScanner fails when Datanode has too many blo

Planning Apache Hadoop 2.7.2

Hi all, We released 2.7.1 nearly 2.5 months ago. I got caught up with a very long release process for 2.6.1 so couldn't make progress on a 2.7.2. Now is the time! Things to do (#1) Branch -- Branch 2.7 has been open to 2.7.2 commits for a while. -- In order to converge on a release, I

Planning for Apache Hadoop 2.6.2

Hi all, Now that 2.6.1 is done, it’s time to look forward to 2.6.2. Things to take care of: (#1) Branch: — The first step in this is getting the branch ready. — As I mentioned before [1], the plan is to rebase branch-2.6 based off branch-2.6.1 i.e. start with 2.6.1 + add patches

[VOTE] Release Apache Hadoop 2.6.1 RC1

Hi all, After a nearly month long [1] toil, with loads of help from Sangjin Lee and Akira Ajisaka, and 153 (RC0)+7(RC1) commits later, I've created a release candidate RC1 for hadoop-2.6.1. RC1 is RC0 [0] (for which I opened and closed a vote last week) + UI fixes for the issue Sangjin raised

Re: [VOTE] Release Apache Hadoop 2.6.1 RC0

One more popped in from Jeff Zhang from Apache Tez: YARN-4154. Looking at that too for RC1. Thanks +Vinod > On Sep 11, 2015, at 11:37 AM, Vinod Kumar Vavilapalli > <vino...@hortonworks.com> wrote: > > Thanks Sangjin and Akira for finding the bug and the fix! > > Th

Re: [VOTE] Release Apache Hadoop 2.6.1 RC0

t; Is anyone else able to reproduce the issue? I checked 2.6.0, and it works >> fine on 2.6.0. >> >> On Wed, Sep 9, 2015 at 6:00 PM, Vinod Kumar Vavilapalli <vino...@apache.org> >> wrote: >> >>> Hi all, >>> >>> After a nearly mont

2.6.1 follow up activities [Was Re: [VOTE] Release Apache Hadoop 2.6.1 RC0]

Forking thread for these follow up activities. One more thing to do - Updating CHANGES.txt entries to reflect the patch-move up to 2.6.1 Thanks +Vinod On Sep 9, 2015, at 6:00 PM, Vinod Kumar Vavilapalli <vino...@apache.org<mailto:vino...@apache.org>> wrote: - Note that bran

Re: [VOTE] Release Apache Hadoop 2.6.1 RC0

> On Sep 10, 2015, at 10:55 AM, Allen Wittenauer <a...@altiscale.com> wrote: > > > On Sep 9, 2015, at 6:00 PM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > >> - Note that branch-2.6 which will be the base for 2.6.2 doesn't have these >> fixes yet.

Re: 2.6.1 follow up activities [Was Re: [VOTE] Release Apache Hadoop 2.6.1 RC0]

I’ve finished this one too. Trunk, branch-2, branch-2.7 and branch-2.6 reflect the backports. I haven’t touched the point branches like 2.7.1. Thanks +Vinod On Sep 10, 2015, at 10:48 AM, Vinod Kumar Vavilapalli <vino...@hortonworks.com<mailto:vino...@hortonworks.com>> wrot

Re: 2.6.1 follow up activities [Was Re: [VOTE] Release Apache Hadoop 2.6.1 RC0]

I have just finished this. Thanks +Vinod On Sep 10, 2015, at 10:48 AM, Vinod Kumar Vavilapalli <vino...@hortonworks.com<mailto:vino...@hortonworks.com>> wrote: - Patches that got into 2.6.1 all the way from 2.8 are NOT in 2.7.2 yet, this will be done as a followup.

[VOTE] Release Apache Hadoop 2.6.1 RC0

Hi all, After a nearly month long [1] toil, with loads of help from Sangjin Lee and Akira Ajisaka, and 153 commits later, I've created a release candidate RC0 for hadoop-2.6.1. The RC is available at: http://people.apache.org/~vinodkv/hadoop-2.6.1-RC0/ The RC tag in git is: release-2.6.1-RC0

Re: Planning Hadoop 2.6.1 release

release. Any dates planned for the release? Nikhil On Fri, Aug 14, 2015 at 12:23 PM, Vinod Kumar Vavilapalli < vino...@hortonworks.com<mailto:vino...@hortonworks.com>> wrote: To clarify, there is already a branch-2.6.1 created separately. So, if you want something in 2.6.2, you can conti

Re: Planning Hadoop 2.6.1 release

. Thanks, Wangda On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee sj...@apache.org wrote: See my later update in the thread. HDFS-7704 is in the list. Thanks, Sangjin On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Makes sense, it was caused by HDFS

Re: Planning Hadoop 2.6.1 release

To clarify, there is already a branch-2.6.1 created separately. So, if you want something in 2.6.2, you can continue putting it in branch-2.6. But no 2.6.1 related commits please. Thanks +Vinod On Aug 14, 2015, at 12:09 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Everyone

Re: Hadoop 2.6.1 Release process thread

Put the list here: https://wiki.apache.org/hadoop/Release-2.6.1-Working-Notes. And started figuring out ways to fast-path the cherry-picks. Thanks +Vinod On Aug 11, 2015, at 1:15 PM, Vinod Kumar Vavilapalli vino...@apache.orgmailto:vino...@apache.org wrote: (2) With Wangda's help offline, I

Hadoop 2.6.1 Release process thread

Hi all, We had a long release-related discussion for 2.6.1 [1], and we pooled in a big list of patches [2]. Together with Akira and Sangjin who offered help with the release, I am starting the release process. Things to do (1) Create 2.6.1 branch and prep branch-2.6 for 2.6.2. I am doing this

Re: Hadoop 2.6.1 Release process thread

This is done. Thanks +Vinod On Aug 11, 2015, at 1:15 PM, Vinod Kumar Vavilapalli vino...@apache.orgmailto:vino...@apache.org wrote: (1) Create 2.6.1 branch and prep branch-2.6 for 2.6.2. I am doing this today.

Re: Hadoop 2.6.1 Release process thread

-7704 is not in the list, we should not backport HDFS-7916 as it fixes an issue introduced by HDFS-7704. On Tue, Aug 11, 2015 at 4:10 PM, Vinod Kumar Vavilapalli vino...@hortonworks.commailto:vino...@hortonworks.com wrote: Put the list here: https://wiki.apache.org/hadoop/Release-2.6.1-Working

Re: Planning Hadoop 2.6.1 release

As of now, I am freezing the list. We have 139 tickets to go through, find the right order, get them committed etc. I’ll start a separate thread for this one-time long release-process of 2.6.1. Thanks everyone for pitching in. +Vinod On Aug 10, 2015, at 4:13 PM, Vinod Kumar Vavilapalli vino

Re: Planning Hadoop 2.6.1 release

cause lots of issue in a large cluster. Thanks, Wangda On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee sj...@apache.org wrote: See my later update in the thread. HDFS-7704 is in the list. Thanks, Sangjin On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com

Re: Planning Hadoop 2.6.1 release

is in the list. Thanks, Sangjin On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only and is not part of the candidate list. Removed HDFS-7916 from the list. Thanks +Vinod On Jul 24, 2015

Re: Planning Hadoop 2.6.1 release

Kumar Vavilapalli vino...@hortonworks.com wrote: Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only and is not part of the candidate list. Removed HDFS-7916 from the list. Thanks +Vinod On Jul 24, 2015, at 6:32 PM, Sangjin Lee sj...@apache.org wrote: Out of the JIRAs

Re: Planning Hadoop 2.6.1 release

in a large cluster. Thanks, Wangda On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee sj...@apache.org wrote: See my later update in the thread. HDFS-7704 is in the list. Thanks, Sangjin On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Makes

Re: Planning Hadoop 2.6.1 release

lots of issue in a large cluster. Thanks, Wangda On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee sj...@apache.org wrote: See my later update in the thread. HDFS-7704 is in the list. Thanks, Sangjin On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote

Re: Planning Hadoop 2.6.1 release

Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only and is not part of the candidate list. Removed HDFS-7916 from the list. Thanks +Vinod On Jul 24, 2015, at 6:32 PM, Sangjin Lee sj...@apache.org wrote: Out of the JIRAs we proposed, please remove HDFS-7916. I don't think it

Re: Planning Hadoop 2.6.1 release

Tx for the list, Joep! Jiras not yet marked with 2.6.1-candidate that we'd like to see in 2.6.1: A whole bunch of them already are marked so, presumably from my list. I’ve added the remaining for discussion. HDFS-7281 (committed in 3.0) This is an incompatible change, so not adding it.

Re: Planning Hadoop 2.6.1 release

-11934 * HADOOP-11491 Thanks, Akira On 7/18/15 11:13, Vinod Kumar Vavilapalli wrote: - I also have a bunch of patches that I’d like to include, will update them right away. I’ve just finished this. The latest 2.6.1-candidate list is up at 64 JIRAs. Others, please look at the list

Re: Planning Hadoop 2.6.1 release

, at 6:24 PM, Vinod Kumar Vavilapalli vino...@hortonworks.commailto:vino...@hortonworks.com wrote: Alright, I’d like to make progress while the issue is hot. I created a label to discuss on the candidate list of patches: https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.6.1-candidatehttps

Re: Planning Hadoop 2.6.1 release

. Thanks +Vinod On Jul 15, 2015, at 1:12 PM, Vinod Kumar Vavilapalli vino...@hortonworks.commailto:vino...@hortonworks.com wrote: Got pinged on a recent thread on this one. As I mentioned there, I had many offline discussions re 2.6.1. The biggest problem I found offline was about what bug-fixes

2.7.2 release plan

Hi all, Thanks everyone for the push on 2.7.1! Branch-2.7 is now open for commits to a 2.7.2 release. JIRA also now has a 2.7.2 version for all the sub-projects. Continuing the previous 2.7.1 thread on steady maintenance releases [1], we should follow up 2.7.1 with a 2.7.2 within 4 weeks.

Re: Planning Hadoop 2.6.1 release

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

Re: [RESULT][VOTE] Release Apache Hadoop 2.7.1 RC0

The website and mirrors updates came back. Sending out an announcement now. Thanks +Vinod On Jul 6, 2015, at 4:31 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Here’s my +1 to end the vote. With 6 binding +1s, 12 non-binding +1s, this release-vote passes. Thanks everyone

[RESULT][VOTE] Release Apache Hadoop 2.7.1 RC0

Here’s my +1 to end the vote. With 6 binding +1s, 12 non-binding +1s, this release-vote passes. Thanks everyone who voted! I’ll follow up on the post-voting release process. Thanks +Vinod On Jun 29, 2015, at 1:45 AM, Vinod Kumar Vavilapalli vino...@apache.org wrote: Hi all, I've

[VOTE] Release Apache Hadoop 2.7.1 RC0

Hi all, I've created a release candidate RC0 for Apache Hadoop 2.7.1. As discussed before, this is the next stable release to follow up 2.6.0, and the first stable one in the 2.7.x line. The RC is available for validation at: *http://people.apache.org/~vinodkv/hadoop-2.7.1-RC0/

Re: 2.7.1 status

Starting release process now. Thanks +Vinod On Jun 24, 2015, at 12:15 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: With a bit of effort from a bunch of contributors/committers, we are finally down to zero blocker/critical issues. Unless, the situation changes, I’ll roll

Re: 2.7.1 status

With a bit of effort from a bunch of contributors/committers, we are finally down to zero blocker/critical issues. Unless, the situation changes, I’ll roll an RC in a day or two. This time for real. Thanks +Vinod On Jun 15, 2015, at 2:58 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com

Re: 2.7.1 status

We are down to one blocker and a few critical tickets. I’ll try to push out an RC in a day or two. Thanks +Vinod On Jun 1, 2015, at 10:45 AM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Tx for the move on that JIRA, folks. https://issues.apache.org/jira/issues/?filter

Re: 2.7.1 status

seems like not a regression bug. Looking forward to get these fixed in 2.7.1 Regards Nijel -Original Message- From: Vinod Kumar Vavilapalli [mailto:vino...@hortonworks.com] Sent: 23 May 2015 01:02 To: Hadoop Common; hdfs-dev@hadoop.apache.org; yarn-...@hadoop.apache.org

Re: 2.7.1 status

be added to the blocker list. This is a critical bug in our ability to protect the LDAP connection password in LdapGroupsMapper. thanks! --larry On Tue, May 26, 2015 at 3:32 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Tx for reporting this, Elliot. Made

Re: 2.7.1 status

Tx for reporting this, Elliot. Made it a blocker, not with a deeper understanding of the problem. Can you please chime in with your opinion and perhaps code reviews? Thanks +Vinod On May 26, 2015, at 10:48 AM, Elliott Clark ecl...@apache.org wrote: HADOOP-12001 should probably be added to

Re: Bug Bash Details/Registration: May 8th, 2015

Would definitely love to participate. I am thinking of spending some time this weekend to do one pass (as a preparation step) atleast in the YARN/MR projects. Will pull in others who have time. Thanks +Vinod On Apr 25, 2015, at 4:02 PM, Allen Wittenauer a...@altiscale.com wrote: (Reply-to

Planning Hadoop 2.6.1 release

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

2.7.1 status

As we talked before [1], I am going to start the push for 2.7.1 [2]. Here are the things I am going to do, with help from others in the community - Review current 2.7.1 content to make sure only bug fixes went in - Review 2.8 to see if any important bug fixes didn't get merged into 2.7.1 -

Re: IMPORTANT: testing patches for branches

Does this mean HADOOP-7435 is no longer needed / closeable as dup? Thanks +Vinod On Apr 22, 2015, at 12:34 PM, Allen Wittenauer a...@altiscale.com wrote: Hey gang, Just so everyone is aware, if you are working on a patch for either a feature branch or a major branch, if you

Re: [RESULT][VOTE] Release Apache Hadoop 2.7.0 RC0

It took a while for the artifact distribution to come around, I initially had trouble pushing them from home too. Anyways, I just updated the website too. Sending an announcement now.. Thanks, +Vinod On Apr 20, 2015, at 8:06 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: With 22

[DISCUSS] Release numbering for stable 2.8 and beyond

/ogzk4phj6wsdpssu On Apr 21, 2015, at 4:59 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Sure, I agree it's better to have clear guidelines and scheme. Let me fork this thread about that. Re 2.7.0, I just forgot about the naming initially though I was clear in the discussion/voting

Re: [DISCUSS] Looking to a 2.8.0 release

includes in next release? Thanks Regards Rohith Sharma K S -Original Message- From: Vinod Kumar Vavilapalli [mailto:vino...@apache.org] Sent: 22 April 2015 03:09 To: common-...@hadoop.apache.org; yarn-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; mapreduce

[DISCUSS] Looking to a 2.8.0 release

With 2.7.0 out of the way, and with more maintenance releases to stabilize it, I propose we start thinking about 2.8.0. Here's my first cut of the proposal, will update the Roadmap wiki. - Support *both* JDK7 and JDK8 runtimes: HADOOP-11090 - Compatibility tools to catch backwards, forwards

Re: [DISCUSS] Looking to a 2.8.0 release

minor release, and start stabilizing as soon as those are in? On Tue, Apr 21, 2015 at 2:39 PM, Vinod Kumar Vavilapalli vino...@apache.orgmailto:vino...@apache.org wrote: With 2.7.0 out of the way, and with more maintenance releases to stabilize it, I propose we start thinking about 2.8.0. Here's

[RESULT][VOTE] Release Apache Hadoop 2.7.0 RC0

With 22 +1s (7 binding), one +0 and no -1s the vote passes. Thanks for everyone who tried the release and voted. I'll push the bits and send out an announcement. Thanks +Vinod On Apr 10, 2015, at 4:44 PM, Vinod Kumar Vavilapalli vino...@apache.org wrote: Hi all, I've created a release

Re: [VOTE] Release Apache Hadoop 2.7.0 RC0

against current 2.6.0. Thanks. patw - Forwarded Message - From: Vinod Kumar Vavilapalli vino...@apache.org To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org Cc: vino...@apache.org Sent: Friday, April 10

[VOTE] Release Apache Hadoop 2.7.0 RC0

Hi all, I've created a release candidate RC0 for Apache Hadoop 2.7.0. The RC is available at: http://people.apache.org/~vinodkv/hadoop-2.7.0-RC0/ The RC tag in git is: release-2.7.0-RC0 The maven artifacts are available via repository.apache.org at

Re: 2.7 status

=12330598 +Vinod On Mar 25, 2015, at 11:47 AM, Konstantin Shvachko shv.had...@gmail.com wrote: Progress is good! What are the four blockers? Could you please mark them as such in the Jira. Thanks, --Konst On Wed, Mar 25, 2015 at 9:53 AM, Vinod Kumar Vavilapalli vino

Re: 2.7 status

A couple of weeks late, but we are here. There is one last blocker that I am about to commit in a little while. I am starting the release process. +Vinod On Mar 25, 2015, at 9:53 AM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Progress has been really slow, but now we are down

A 2.7.1 release to follow up 2.7.0

Hi all, I feel like we haven't done a great job of maintaining the previous 2.x releases. Seeing as how long 2.7.0 release has taken, I am sure we will spend more time stabilizing it, fixing issues etc. I propose that we immediately follow up 2.7.0 with a 2.7.1 within 2-3 weeks. The focus

Re: IMPORTANT: automatic changelog creation

We'd then doing two commits for every patch. Let's simply not remove CHANGES.txt from trunk, keep the existing dev workflow, but doc the release process to remove CHANGES.txt in trunk at the time of a release going out of trunk. +Vinod On Apr 2, 2015, at 10:12 AM, Allen Wittenauer

Re: 2.7 status

Progress has been really slow, but now we are down to four blockers across the board. I plan to roll an RC this weekend. Thanks, +Vinod On Mar 8, 2015, at 8:40 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: 2.7 branch created and branch-2 updated to point to 2.8-SNAPSHOT

Re: Looking to a Hadoop 3 release

On Mar 6, 2015, at 5:20 PM, Chris Douglas cdoug...@apache.org wrote: On Fri, Mar 6, 2015 at 4:32 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: I'd encourage everyone to post their wish list on the Roadmap wiki that *warrants* making incompatible changes forcing us to go 3.x

Re: 2.7 status

Branching 2.7 now. Request holding off commits to branch-2 to avoid commit race. Will send an all-clear in the next 30 mins once I am done. Thanks +Vinod On Mar 5, 2015, at 1:56 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: The 2.7 blocker JIRA went down and going back up

Re: 2.7 status

Vavilapalli vino...@hortonworks.com wrote: Branching 2.7 now. Request holding off commits to branch-2 to avoid commit race. Will send an all-clear in the next 30 mins once I am done. Thanks +Vinod On Mar 5, 2015, at 1:56 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote

Re: Looking to a Hadoop 3 release

, 2015 at 2:32 PM, Arun Murthy a...@hortonworks.com wrote: Awesome, looks like we can just do this in a compatible manner - nothing else on the list seems like it warrants a (premature) major release. Thanks Vinod. Arun From: Vinod Kumar Vavilapalli

Re: Looking to a Hadoop 3 release

Yes, these are the kind of enhancements that need to be proposed and discussed for inclusion! Thanks, +Vinod On Mar 5, 2015, at 3:21 PM, Siddharth Seth ss...@apache.org wrote: Some features that come to mind immediately would be 1) enhancements to the RPC mechanics - specifically support

Re: Looking to a Hadoop 3 release

The 'resistance' is not so much about a new major release, more so about the content and the roadmap of the release. Other than the two specific features raised (the need for breaking compat for them is something that I am debating), I haven't seen a roadmap of branch-3 about any more features

Re: Looking to a Hadoop 3 release

Moving to JDK8 involves a lot of things (1) Get Hadoop apps to be able to run on JDK8 and chose JDK8 language features. This is already possible with the decoupling of apps from the platform. (2) Get the platform to run on JDK8. This can be done so that we can run Hadoop on both JDK8 and

Re: 2.7 status

a...@hortonworks.com wrote: Sounds good, thanks for the help Vinod! Arun From: Vinod Kumar Vavilapalli Sent: Sunday, March 01, 2015 11:43 AM To: Hadoop Common; Jason Lowe; Arun Murthy Subject: Re: 2.7 status Agreed. How about we roll an RC end

Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches

on JIRA and get this in. On Wed, Mar 4, 2015 at 1:20 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Hi all, I'd like us to revive the effort at https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit builds being able to work with branches. Having the Jenkins verify

Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches

Hi all, I'd like us to revive the effort at https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit builds being able to work with branches. Having the Jenkins verify patches on branches is very useful even if there may be relaxed review oversight on the said-branch. Unless there

Re: Looking to a Hadoop 3 release

I started pitching in more on that JIRA. To add, I think we can and should strive for doing this in a compatible manner, whatever the approach. Marking and calling it incompatible before we see proposal/patch seems premature to me. Commented the same on JIRA:

<    1   2   3   >