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 w

[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/

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 tags

Re: [VOTE] Release Apache Hadoop 2.7.2 RC0

-4354 > <https://issues.apache.org/jira/browse/YARN-4354>. We need that resolved > before the release is ready. We will either need a timely fix or may have to > revert YARN-2902 to unblock the release if my root-cause analysis is correct. > I'll dig into this more to

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 Wangda

Re: [DISCUSS] Looking to a 2.8.0 release

There are 40 odd incompatible changes in 3.x: https://issues.apache.org/jira/issues/?jql=project%20in%20%28HADOOP%2C%20YARN%2C%20HDFS%2C%20MAPREDUCE%29%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%203.0.0%20AND%20fixVersion%20not%20in%20%282.6.2%2C%202.6.3%2C%202.7.1%2C%202.7.2%2C%202

Re: [DISCUSS] Looking to a 2.8.0 release

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 > wrote: > > - Cut a branch about two weeks from now > - Do an RC mid next month (leaving ~

Re: [DISCUSS] Looking to a 2.8.0 release

y 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 > > > > > On 11

Re: [DISCUSS] Looking to a 2.8.0 release

se that 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 Vavilapa

[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 upda

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 now in or

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: 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 > wrote: > > That makes sense. > &

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 tags as they > should

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 > wrote: > > So, the original voting mail mentions we are voting on release-2.6.3-RC0 tag. > > Are we still doing that? What are the

Re: [VOTE] Release Apache Hadoop 2.7.2 RC0

nto 2.7.2? > > Cos > > On Mon, Nov 30, 2015 at 01:25PM, Vinod Kumar Vavilapalli wrote: >> I think we should get it in, I am still stuck on a couple of HDFS patches. >> >> But I was not sure overall if the patch was right. Commented on the JIRA >> regarding the sa

Re: [VOTE] Release Apache Hadoop 2.7.2 RC0

15, 2015, at 12:59 AM, Konstantin Shvachko > 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, 2015 at 8:31 PM, Vinod Kumar

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 > wrote: > > Thanks for reporting this Jason! > > Everyone, I am canceling this RC given the feedback, we will go again after >

[VOTE] Release Apache Hadoop 2.7.2 RC1

Hi all, I've created a release candidate RC1 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-RC1/

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

Not entirely sure we have enough info to warrant a hard-reset. Yet. Do we know how many of these are new features / improvement that we shouldn’t put any more into 2.8.0 and how many are bugs that we need to? If you don’t have time, I’ll look at it right after getting out 2.7.2 RC1. Thanks +Vin

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

> --Konst > > On Wed, Dec 16, 2015 at 6:52 PM, Vinod Kumar Vavilapalli > wrote: > >> Not entirely sure we have enough info to warrant a hard-reset. Yet. >> >> Do we know how many of these are new features / improvement that we >> shouldn’t put any more int

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 / improvements

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 > wrote: > > Wangda, > > I see just 13 tickets *only in 2.9.0* > (https://issues.apache

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 AM,

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

anks +Vinod > On Dec 23, 2015, at 12:37 PM, Vinod Kumar Vavilapalli > 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. > > Reverting my +1, and casting -1

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

ivial (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 Kumar Vavilapalli mailto:vino...@apac

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

ncat,TestLineRecordReader,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 > wrote: > > Thanks for the comments Tsuyos

[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 no

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. > Summarizi

[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 m

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

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

s 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-nodes to false. > Jason > > >

Re: Release numbering for branch-2 releases

I still have a list of pending API/protocol cleanup in YARN that need to be in before we even attempt supporting compatibility further down the road. There's no way we can support wire compatibility with the APIs in the state that they are in now. So, +1 for a beta sometime in March. There are som

Re: [VOTE] Release Apache Hadoop 2.0.4-alpha

Sid, I checked this into 2.0.4-alpha. Thanks, +Vinod On Apr 9, 2013, at 11:14 PM, Siddharth Seth wrote: > Arun, MAPREDUCE-5094 would be a useful jira to include in the 2.0.4-alpha > release. It's not an absolute blocker since the values can be controlled > explicitly by changing tests which use

Re: [VOTE] Release Apache Hadoop 2.0.4-alpha

Talked to Arun offline and merged this into 2.0.4-alpha. Also fixed CHANGES.txt. Thanks, +Vinod On Apr 10, 2013, at 9:10 PM, Alejandro Abdelnur wrote: > I've comitted HADOOP-9471 to trunk and branch-2 and closed JIRA with > fixedVersion 2.0.5. > > If this JIRA makes it to 2.0.4 we need to upda

Re: Cannot communicate

It means what it says: that hadoop native library isn't available for some reason. See http://hadoop.apache.org/docs/stable/native_libraries.html Thanks, +Vinod Kumar Vavilapalli Hortonworks Inc. http://hortonworks.com/ On Apr 22, 2013, at 9:58 AM, rkevinbur...@charter.net wrote: > I

Re: [VOTE] Release Apache Hadoop 2.0.4.1-alpha

This started out as something and ended up as something else altogether. In any case, I think you should give a fresh heads up outside this thread. There are a bunch of commits and merges happening into branch-2 and thus 2.0.5, so it'll be safe to have an explicit hold-off/all-clear signaling.

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

We should get these in, looking at them now. Thanks, +Vinod On Jun 28, 2013, at 12:03 PM, Hitesh Shah wrote: > Hi Arun, > > From a YARN perspective, YARN-791 and YARN-727 are 2 jiras that may > potentially change the apis. They can implemented in a backward compat > fashion if committed aft

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

that we can create a fresh release branch and call voting on that. I'll fix CHANGES.txt entries as well as JIRA fix version for bugs committed recently if there are inconsistencies. Let me know if something is amiss while I do this. Thanks, +Vinod On Jul 3, 2013, at 11:06 AM, Vinod Kumar V

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

On Jul 17, 2013, at 1:04 PM, Alejandro Abdelnur wrote: > * YARN-701 > > It should be addressed before a GA release. > > Still, as it is this breaks unmanaged AMs and to me > that would be a blocker for the beta. > > YARN-701 and the unmanaged AMs fix should be committed > in tandem. > > * YAR

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

We need to make a call on what blockers will be. From my limited understanding, this doesn't seem like a API or a compatibility issue. Can we not fix it in subsequent bug-fix releases? I do see a lot of follow up releases to 2.1.0. Getting this release out will help downstream projects start t

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

Cc: Kihwal Lee ; "mapreduce-...@hadoop.apache.org" >> ; "hdfs-dev@hadoop.apache.org" >> ; "yarn-...@hadoop.apache.org" >> >> Sent: Friday, August 16, 2013 3:44 PM >> Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta >> >> >>

Re: [VOTE] Release Apache Hadoop 2.1.0-beta

release gets >> complete… hopefully next week. >> >> thanks, >> Arun >> >> On Aug 16, 2013, at 4:36 PM, Vinod Kumar Vavilapalli >> wrote: >> >>> >>> There are other such isolated and well understood bug-fixes that we pushed

Re: hadoop-2.1.1-beta & hadoop-2.2.0 (GA)

Looking at the blockers, MAPREDUCE and YARN at least, looks like we'll need a week or two. A branch 2.1.1 would mean commits to 4 branches. Assuming everyone is only committing blockers, bugs and critical fixes to branch-2.1-beta, we should be okay with not creating yet another branch. Thanks,

Re: [VOTE] Release Apache Hadoop 2.1.1-beta

Correct me if I am wrong, but FWIU, we already released a beta with the same symlink issues. Given 2.1.1 is just another beta, I believe we can go ahead with it and resolve the issues in the final GA release. Instead of resetting the testing done by everyone. It's a hard story to sell but beta

Re: [VOTE] Release Apache Hadoop 2.1.1-beta

I ran through my usual check-list for validating the RC. I only checked the source tarball. - Signatures and message digests all good. I guess because of differences in gpg2's version, the message digest has different text wrapping. Anyways. - The top level full LICENSE, NOTICE and README are g

Re: 2.1.2 (Was: Re: [VOTE] Release Apache Hadoop 2.1.1-beta)

+1. We should get an RC as soon as possible so that we can get all the downstream components to sign off. The earlier the better. Thanks, +Vinod On Oct 1, 2013, at 4:15 PM, Arun C Murthy wrote: > Guys, > > I took a look at the content in 2.1.2-beta so far, other than the critical > fixes such

Re: [Proposal] Pluggable Namespace

In order to make federation happen, the block pool management was already separated. Isn't that the same as this effortt? Thanks, +Vinod On Oct 6, 2013, at 9:35 AM, Milind Bhandarkar wrote: > Federation is orthogonal with Pluggable Namespaces. That is, one can use > Federation if needed, even w

Re: [Proposal] Pluggable Namespace

Milind/Andrew and everyone else, Didn't know an innocuous question regarding a technical issue can blow up so much. I asked a technical question. If you have an answer and you want to respond, please do so. If you don't have an answer, you can reply so. Otherwise please keep this thread for t

Re: [VOTE] Release Apache Hadoop 2.2.0

Ran through my usual check-list. - Signatures and message digests all good. - The top level full LICENSE, NOTICE and README files look fine. - CHANGES.txt for common, hdfs, yarn and mapped are located as in before releases. - Able to build the tars out of the source tar ball. Testing: Built

Re: Is it me or is the new bootstrap HDFS UI HWX green? (See tip of hadoop-2.3 branch)

This is unbelievable. This was not deliberate for all I know. It is one of the user-names on a machine and it can be anything. So, from on, I cannot build and roll a release candidate from my laptop which has usernames set to Company*user-name ? Can you stop digging into trifles of this kind a

Re: Is it me or is the new bootstrap HDFS UI HWX green? (See tip of hadoop-2.3 branch)

My response was to your direct association of the green color to HWX green as if it were deliberately done. Nobody here intentionally left a vendor's signature like you claimed. And to your other comment "Does the apache binary have to be compiled by 'hortonmu'? Could it be compiled by 'arun'

Re: Re-swizzle 2.3

Okay, I'll look at YARN and MR CHANGES.txt problems. Seems like they aren't addressed yet. +Vinod On Jan 29, 2014, at 3:24 PM, Andrew Wang wrote: > I just finished tuning up branch-2.3 and fixing up the HDFS and Common > CHANGES.txt in trunk, branch-2, and branch-2.3. I had to merge back a f

Re: Re-swizzle 2.3

That was quite some exercise, but I'm done with it now. Updated YARN's and MAPREDUCE's CHANGES.txt on trunk, branch-2 and branch-2.3. Let me know if you find some inaccuracies. Thanks, +Vinod On Jan 29, 2014, at 10:49 PM, Vinod Kumar Vavilapalli wrote: > > Okay, I&#

Re: Re-swizzle 2.3

That's right. +Vinod On Jan 31, 2014, at 5:25 PM, Andrew Wang wrote: > YARN-1673 IIUC relates to the AHS, so is actually only in branch-2 and not > branch-2.3. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may

Re: [DISCUSS] Looking to Apache Hadoop 3.1 release

Thanks for starting this thread, Wangda! +1 for establishing a faster cadence now itself. One word of caution though. The same I expressed while we were trying to do both 2.8 and 3.0 releases at the same time. Please try avoiding concurrent releases and splitting community bandwidth - it's not

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

> At a minimum, it should at least be using it’s own maven module for a > lot of the bits that generates it’s own maven jars so that we can split this > functionality up at build/test time. I expected this to be the case, but looks like it isn't. There's lot of value in splitting the HDF

Re: [VOTE] Release Apache Hadoop 2.9.0 (RC0)

Arun / Subru, Thanks for the great work! Few quick comments - Can you cleanup the RC folder to only have tar.gz and src.tar.gz and their signatures and delete everything else? So that it's easy to pick up the important bits for the voters. For e.g, like this http://people.apache.org/~vinodkv/

[DISCUSS] A final minor release off branch-2?

Hi all, With 3.0.0 GA around the corner (tx for the push, Andrew!), 2.9.0 RC out (tx Arun / Subru!) and 2.8.2 (tx Junping!), I think it's high time we have a discussion on how we manage our developmental bandwidth between 2.x line and 3.x lines. Once 3.0 GA goes out, we will have two parallel

Re: [VOTE] Merge yarn-native-services branch into trunk

and have no impact on existing system if disabled. > > Special thanks to a team of folks who worked hard towards this: Billie > Rinaldi, Gour Saha, Vinod Kumar Vavilapalli, Jonathan Maron, Rohith Sharma K > S, Sunil G, Akhil PB, Eric Yang. This effort could not be possible without >

Re: [DISCUSS] A final minor release off branch-2?

Use the opportunity to clean up deprecated API ? >> * Do we even want to consider a separate bridging release for 2.7, 2.8 an >> 2.9 lines ? >> >> Cheers >> -Arun >> >> On Fri, Nov 3, 2017 at 5:07 PM, Vinod Kumar Vavilapalli < >> vino...@apac

Re: [DISCUSS] A final minor release off branch-2?

e. I'd like option C), and suggest we focus on the recent > releases. Answering this question is also one of the goals of my starting this thread. Collectively we need to conclude if we are okay or not okay with no longer putting any new feature work in general on the 2.x line after 2.9

Re: [VOTE] Release Apache Hadoop 2.9.0 (RC0)

A related point - I thought I mentioned this in one of the release preparation threads, but in any case. Starting 2.7.0, for every .0 release, we've been adding a disclaimer (to the voting thread as well as the final release) that the first release can potentially go through additional fixes to

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

I'd definitely extend it for a few more days. I only see 3 binding +1s so far - not a great number to brag about on our first major release in years. Also going to nudge folks into voting. +Vinod > On Nov 17, 2017, at 3:26 PM, Andrew Wang wrote: > > Hi Arpit, > > I agree the timing is not gr

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

Quick question. I used to be able (in 2.x line) to create dist tarballs (mvn clean install -Pdist -Dtar -DskipTests -Dmaven.javadoc.skip=true) from the source being voted on (hadoop-3.0.0-src.tar.gz). The idea is to install HDFS, YARN, MR separately in separate root-directories from the genera

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

> 1.8.0_151 > Maybe it would be a good idea to name a list of JDKs that are known to be > buggy. Can we get this documented somewhere? I don't consider it a blocker > so a release note in a later release or a wiki entry should be good enough. > > On Mon, Nov 20, 2017 at 12

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

Thanks for all the push, Andrew! Looking at the RC. Went through my usual check-list. Here's my summary. Will cast my final vote after comparing and validating my findings with others. Verification - [Check] Successful recompilation from source tar-ball - [Check] Signature verification - [Ch

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

>> - One decommissioned node in YARN ResourceManager UI always appears to >> start with, even when there are no NodeManagers that are started yet: >> Info :-1, DECOMMISSIONED, null rack. It shows up only in the UI though, >> not in the CLI node -list >> > > Is this a blocker? Could we get a JIRA?

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

>>> - Cannot enable new UI in YARN because it is under a non-default >>> compilation flag. It should be on by default. >>> >> >> The yarn-ui profile has always been off by default, AFAIK. It's documented >> to turn it on in BUILDING.txt for release builds, and we do it in >> create-release. >> >

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

>> - $HADOOP_YARN_HOME/sbin/yarn-daemon.sh start historyserver doesn't even >> work. Not just deprecated in favor of timelineserver as was advertised. > > This works for me in trunk and the bash code doesn’t appear to have > changed in a very long time. Probably something local to your in

Re: [VOTE] Release Apache Hadoop 2.9.0 (RC0)

nd those tradeoffs, since they depend on internal details of > Hadoop. > > On Wed, Nov 8, 2017 at 5:34 PM, Vinod Kumar Vavilapalli > mailto:vino...@apache.org>> wrote: >> When we tried option (b), we used to make .0 as a GA release, but downstream >> projects like T

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

I couldn't find the release tag for RC1 either - is it just me or has the release-process changed? +Vinod > On Dec 10, 2017, at 4:31 PM, Sangjin Lee wrote: > > Hi Andrew, > > Thanks much for your effort! Just to be clear, could you please state the > git commit id of the RC1 we're voting for?

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

Looked at RC1. Went through my usual check-list. Here's my summary. +1 (binding) overall Verification - [Check] Successful recompilation from source tar-ball - [Check] Signature verification - [Check] Generating dist tarballs from source tar-ball - [Check] Validating the layout of the binary tar-

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

I was waiting for Daniel to post the minutes from YARN meetup to talk about this. Anyways, in that discussion, we identified a bunch of key upgrade related scenarios that no-one seems to have validated - atleast from the representation in the YARN meetup. I'm going to create a wiki-page listing

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

Good stuff Andrew, and thanks everyone! +Vinod > On Dec 13, 2017, at 1:05 PM, Andrew Wang wrote: > > To close this out, the vote passes successfully with 13 binding +1s, 5 > non-binding +1s, and no -1s. Thanks everyone for voting! I'll work on staging. >

Re: [VOTE] Release Apache Hadoop 3.0.0 RC1

Yes, JIRAs will be filed, the wiki-page idea from YARN meetup is to record all combinations of testing that need to be done and correspondingly capture all the testing that someone in the community has already done and record it for future perusal. From what you are saying, I guess we haven't a

Re: [EVENT] HDFS Bug Bash: March 12

Was out of country and away from email for weeks. We have been using this in the past: https://www.meetup.com/Hadoop-Contributors/ . I believe this doesn't have the per-meetup-charge issue, but will double check. Let me know if there are more meetup

Re: About reset branch-3.1 to trunk before release.

I see one new feature: https://issues.apache.org/jira/browse/YARN-7626: Allow regular expression matching in container-executor.cfg for devices and named docker volumes mount. There are 21 sub-tasks. There are three feature-type JIRAs in those - https://issues.apache.org/jira/browse/YARN-7972,

Re: About reset branch-3.1 to trunk before release.

>>>> >>>>> Thanks for sharing your thoughts. >>>>> >>>>> We have done build and single node cluster deploy / test for the >> latest >>>>> trunk code (commit: 49c747ab187d0650143205ba57ca19607ec4c6bd). >> Since >&

Re: [VOTE] Adopt HDSL as a new Hadoop subproject

Glad to see consensus on this proposal. This new subproject will hopefully continue Hadoop's evolution forward (dare I say the biggest one since YARN) and also intends to accomplish this with minimal project overhead. +1 binding. Thanks +Vinod > On Mar 20, 2018, at 11:20 AM, Owen O'Malley wr

Re: [VOTE] Release Apache Hadoop 3.1.0 (RC1)

<mailto:hdfs-dev@hadoop.apache.org>>, Hadoop Common > mailto:common-...@hadoop.apache.org>>, > "mapreduce-...@hadoop.apache.org <mailto:mapreduce-...@hadoop.apache.org>" > mailto:mapreduce-...@hadoop.apache.org>>, > Vinod Kumar Vavilapalli mail

Re: [VOTE] Release Apache Hadoop 3.1.0 (RC1)

come from our release process. > > Thanks, > Wangda > > [1] Maven jars are downloaded from > https://repository.apache.org/service/local/repositories/releases/content/org/apache/hadoop/hadoop-yarn-api/ > /hadoop-yarn-api-.jar > [2] Binary tarballs downloaded from http://apache.

Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

I will add that the branch also successfully compiles. Let's just move forward as is, unblock commits and just fix things if anything is broken. +Vinod > On Jul 6, 2018, at 10:30 AM, Anu Engineer wrote: > > Hi All, > > [ Thanks to Arpit for working offline and verifying that branch is indeed

Re: [VOTE] reset/force push to clean up inadvertent merge commit pushed to trunk

, YARN-7556, YARN-7451 >> are not anymore in trunk due to the revert. >> >> Haibo/Robert if you can recommit your patches I will commit mine >> subsequently to preserve the original order. >> >> (My apology for the mess I did with the merge commit) >

Re: [VOTE] Release Apache Hadoop 3.0.3 (RC0)

Yongjun, Looks like you didn't add the links to 3.0.3 binary release on the http://hadoop.apache.org/releases.html page. I just did it, FYI: https://svn.apache.org/viewvc?view=revision&revision=1837967 Thanks +Vinod > On May 31,

Re: HADOOP-14163 proposal for new hadoop.apache.org

(for example new >> release announcements could be generated as part of the release process) >> I think it's very low risk to try out a new approach for the site (and easy >> to rollback in case of problems) >> Marton >> ps: I just updated the patch/preview site

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

ave a plan for that soon. > +1 (binding) for 2.7.2 RC2. > Jason > > > From: Vinod Kumar Vavilapalli > To: mapreduce-...@hadoop.apache.org; Jason Lowe > Cc: Hadoop Common ; > "hdfs-dev@hadoop.apache.org" ; > "yarn-...@hadoop.apache.org" > Sen

Re: [VOTE] Release Apache Hadoop 2.7.2 RC2

Eric, is there a JIRA for this? +Vinod > On Jan 19, 2016, at 2:27 PM, Eric Payne > wrote: > > One minor issue is that when the job was running on the labelled queue, it > ran fine but the cluster scheduler web UI showed a blank status bar for that > queue in the "Application Queues" section.

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 > wrote: > > Hi all, > > I

[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 > wrote: > > Hi all, > > I

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

f of Sangjin Lee <mailto:sj...@apache.org>> > Sent: Friday, January 15, 2016 7:17 AM > To: yarn-...@hadoop.apache.org <mailto:yarn-...@hadoop.apache.org> > Cc: Hadoop Common; hdfs-dev@hadoop.apache.org > <mailto:hdfs-dev@hadoop.apache.org>; mapreduce-...@hadoop.apache.or

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

we 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 >> bran

Re: [RESULT][VOTE] Release Apache Hadoop 2.7.2 RC2

Done with all the release-activities, the mirrors came back too. Sending out an announcement. Thanks +Vinod > On Jan 25, 2016, at 9:19 AM, Vinod Kumar Vavilapalli > wrote: > > Here’s my +1 to conclude the vote. > > With 12 binding +1s, 11 non-binding +1s and no -1s

Re: [DISCUSSION] Release Plan for Apache Hadoop 2.6.4

I just pushed out 2.7.2 to the public. Let’s get 2.6.4 back into focus now that 2.7.2 is done. In the mean while, I’ll get go dust off 2.8.0 too .. Thanks +Vinod > On Jan 6, 2016, at 3:59 PM, Junping Du wrote: > > Hello folks, > Hope everyone had a wonderful holiday and good rest in pa

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 >

Re: [Release thread] 2.8.0 release activities

Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma >> >>> wrote: >>> >>>> Thanks Vinod. +1 for 2.8 release start. >>>> >>>> Regards, >>>> Uma >>>> >>>> On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli&qu

Re: 'Target Version' field missing in Jira

I just filed https://issues.apache.org/jira/browse/INFRA-11274 . +Vinod > On Feb 16, 2016, at 10:23 AM, Aaron T. Myers wrote: > > Has anyone followed up with ASF Infra about getting this addressed? I worry > that all the data for the target ve

Re: 'Target Version' field missing in Jira

The data is still intact as I can see that I can continue to search on JIRA against target-version. But only in advanced-search though. +Vinod > On Feb 16, 2016, at 10:23 AM, Aaron T. Myers wrote: > > I worry > that all the data for the target versions has disappeared as well...

Re: 'Target Version' field missing in Jira

It’s back up now. +Vinod > On Feb 16, 2016, at 11:42 AM, Vinod Kumar Vavilapalli > wrote: > > The data is still intact as I can see that I can continue to search on JIRA > against target-version. But only in advanced-search though. > > +Vinod > >> On Feb

2.7.3 release plan

Hi all, Got nudged about 2.7.3. Was previously waiting for 2.6.4 to go out (which did go out mid February). Got a little busy since. Following up the 2.7.2 maintenance release, we should work towards a 2.7.3. The focus obviously is to have blocker issues [1], bug-fixes and *no* features / impr

  1   2   3   >