Re: [DISCUSS] Enable github security notifications to all Hadoop committers

Shouldn’t we instead send this to the security list and let that team make decisions first there? What volume are we looking at? Thanks +Vinod > On Oct 24, 2019, at 12:07 PM, Wei-Chiu Chuang wrote: > > Hi, > I raised INFRA-19327 to > enable

Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree [discussion -> lazy vote]

On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton wrote: > As the overall feedback was positive (in fact many of the answers were > simple +1 votes) I don't think the thread should be repeated under > [VOTE] subject. Therefore I call it for a lazy consensus. > Let's please not do this in the

Re: VOTE PASSED - Hadoop-3.1.3-RC0 Re: [VOTE] Release Hadoop-3.1.3-RC0

Zhankun et.al, Did we close down the rest of the release process for 3.1.3? I don't yet see this on the site, so asking. If it's not done yet and you are running into issues, please let me know and I can help with the corresponding release management tasks. Thanks +Vinod On Tue, Sep 24, 2019

Re: Does VOTE necessary to create a child repo?

Moving the thread to the dev lists. Thanks +Vinod > On Sep 23, 2019, at 11:43 PM, Vinayakumar B wrote: > > Thanks Marton, > > Current created 'hadoop-thirdparty' repo is empty right now. > Whether to use that repo for shaded artifact or not will be monitored in > HADOOP-13363 umbrella jira.

Re: [ANNOUNCE] Apache Hadoop 3.2.1 release

Done: https://twitter.com/hadoop/status/1176787511865008128. If you have tweetdeck, any of the PMC members can do this. BTW, it looks we haven't published any releases since Nov 2018. Let's get back to doing this going forward! Thanks +Vinod > On Sep 25, 2019, at 2:44 PM, Rohith Sharma K S

Re: [NOTICE] Building trunk needs protoc 3.7.1

Quick question, being lazy here, lots of JIRA updates on HADOOP-13363 over the years not helping either. Does anyone know what this upgrade will mean w.r.t compatibility for the Hadoop releases themselves? Remember that trunk is still 3.x. Thanks +Vinod > On Sep 21, 2019, at 9:55 AM,

Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree

Looks to me that the advantages of this additional step are only incremental given that you've already decoupled releases and dependencies. Do you see a Submarine like split-also-into-a-TLP for Ozone? If not now, sometime further down the line? If so, why not do both at the same time? I felt

Re: Any thoughts making Submarine a separate Apache project?

Looks like there's a meaningful push behind this. Given the desire is to fork off Apache Hadoop, you'd want to make sure this enthusiasm turns into building a real, independent but more importantly a sustainable community. Given that there were two official releases off the Apache Hadoop

Re: [DISCUSS] Prefer JUnit5 for new tests

+1 if it is indeed possible to have both. Thanks +Vinod > On Jul 26, 2019, at 1:56 PM, Akira Ajisaka wrote: > > Hi folks, > > Now we are slowly migrating from JUnit4 to JUnit5. > https://issues.apache.org/jira/browse/HADOOP-14693 > > However, as Steve commented [1], if we are going to

Re: [VOTE] Force "squash and merge" option for PR merge on github UI

Makes sense, +1. Thanks +Vinod > On Jul 17, 2019, at 11:37 AM, Elek, Marton wrote: > > Hi, > > Github UI (ui!) helps to merge Pull Requests to the proposed branch. > There are three different ways to do it [1]: > > 1. Keep all the different commits from the PR branch and create one >

Fwd: Incorrect NOTICE files in TLP releases

A bit of an old email, but want to make sure this isn't missed. Has anyone looked into this concern? Ref https://issues.apache.org/jira/browse/ROL-2138 . Thanks +Vinod > Begin forwarded message: > > From: sebb > Subject: Incorrect NOTICE files

Re: June Hadoop Community Meetup

Plus general@ list. Thanks +Vinod > On Jun 4, 2019, at 9:47 PM, Daniel Templeton > wrote: > > The meetup page is now live: > >https://www.meetup.com/Hadoop-Contributors/events/262055924 > > I'll fill in the agenda details after we get them nailed down. The meetup > will be an all-day

Re: Impact of Not Enabling KerberosDelegationTokenAuthenticationHandler

Not sure what your question really is. KerberosDelegationTokenAuthenticationHandler was created mainly to add delegation-token support on top of KerberosAuthenticationHandler. Thanks +Vinod > On May 22, 2019, at 10:58 AM, Prabhu Joseph > wrote: > > Hi, > > Was testing YARN RM with Http

Re: Issue in docs page : single cluster yarn setup - https://hadoop.apache.org/docs/r3.2.0/hadoop-project-dist/hadoop-common/SingleCluster.html#YARN_on_Single_Node

Good catch. Please file a JIRA ticket here: https://issues.apache.org/jira/browse/YARN . Please put a patch up too if you can! The second property is a configuration for MR jobs to figure out where the MapReduce framework libraries are. Thanks

Re: Cannot kill Pre-Commit jenkins builds

Done. Please see if it works for you. Thanks +Vinod > On Feb 14, 2019, at 1:12 PM, Arun Suresh wrote: > > Hello Vinod > > Kindly add me (asuresh) and Jonathan Hung as well.. > > Cheers > -Arun > > On Thu, Feb 14, 2019, 11:46 AM Vinod Kumar Vavilapalli <

Re: [DISCUSS] Moving branch-2 to java 8

The community made a decision long time ago that we'd like to keep the compatibility & so tie branch-2 to Java 7, but do Java 8+ only work on 3.x. I always assumed that most (all?) downstream users build branch-2 on JDK 7 only, can anyone confirm? If so, there may be an easier way to address

Re: [Result] [VOTE] Merge HDFS-12943 branch to trunk - Consistent Reads from Standby

Agree, it isn't productive this way. I can't seem to find it, but was there a DISCUSS thread for this branch-merge? I usually recommend addressing issues on a DISCUSS thread instead of fighting things over a VOTE. +Vinod > On Dec 13, 2018, at 10:09 AM, Konstantin Shvachko > wrote: > > This

Re: [DISCUSS] Move to gitbox

We need to write up the stages of the process and put a concrete timeline first. Is it an atomic move? Or will both repos live at the same time? Do we need a stop-the-world period and messaging sent out? When do the git-wip repos get deleted and/or stop getting updates? Things I can think of

Re: Can someone add me to the JIRA admin list

That's right, there's no policy. It's done on an adhoc/need basis. There is no automated way to put all committers in that ACL. +Vinod > On Dec 13, 2018, at 7:59 AM, Sean Busbey wrote: > > AFAIK we don't have like a policy or something. If folks want to help > on one of the JIRA instances I

Re: Apache Hadoop 3.1.2 release plan

231 fixed JIRAs is already quite a bunch! I only see 7 JIRAs marked with Affects Version 3.1.2 and only one of them as blocker. Why not just release now as soon as there are no blockers? Thanks +Vinod > On Oct 24, 2018, at 4:36 PM, Wangda Tan wrote: > > Hi, All > > We have released Apache

Re: [ANNOUNCE] Apache Hadoop Ozone 0.2.1-alpha release

Congratulations on the release! Just seeing this, why is this its own website with its own downloads section, look & feel etc instead of being part of our larger site? +Vinod > On Oct 1, 2018, at 5:24 PM, Elek, Marton wrote: > > > It gives me great pleasure to announce that the Apache

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 with

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=1837967 Thanks +Vinod > On May 31, 2018, at 10:48

Re: Releases table needs to be cleaned up

Done. Thanks +Vinod > On Jul 2, 2018, at 7:12 AM, Andrew Wang > wrote: > > Hi folks, > > https://hadoop.apache.org/releases.html > > The table of releases here is supposed to only contain one row per release > line. We've got a lot of old dupes at this point, e.g. 3.0.2, 2.9.0, 2.8.3. >

Re: [VOTE] Release Apache Hadoop 2.7.7

Steve, Looks like you didn't add the links to 2.7.7 source release at all on the http://hadoop.apache.org/releases.html page! I just did it, FYI: https://svn.apache.org/viewvc?view=revision=1837966 Thanks +Vinod > On Jul 16, 2018, at

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] 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

[jira] [Created] (HADOOP-15571) After HADOOP-13440, multiple filesystems/file-contexts created with the same Configuration object are forced to have the same umask

Vinod Kumar Vavilapalli created HADOOP-15571: Summary: After HADOOP-13440, multiple filesystems/file-contexts created with the same Configuration object are forced to have the same umask Key: HADOOP-15571

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

Got pinged about this offline. Thanks for keeping at it, Marton! I think there are two road-blocks here (1) Is the mechanism using which the website is built good enough - mvn-site / hugo etc? (2) Is the new website good enough? For (1), I just think we need more committer attention and get

[jira] [Created] (HADOOP-15527) Sometimes daemons keep running even after "kill -9" from daemon-stop script

Vinod Kumar Vavilapalli created HADOOP-15527: Summary: Sometimes daemons keep running even after "kill -9" from daemon-stop script Key: HADOOP-15527 URL: https://issues.apache.org/jira/bro

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

I guess the differences 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 downloa

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

;>, "yarn-...@hadoop.apache.org > <mailto:yarn-...@hadoop.apache.org>" <yarn-...@hadoop.apache.org > <mailto:yarn-...@hadoop.apache.org>>, Hdfs-dev <hdfs-...@hadoop.apache.org > <mailto:hdfs-...@hadoop.apache.org>>, Hadoop Common > <commo

[jira] [Resolved] (HADOOP-13500) Concurrency issues when using Configuration iterator

[ https://issues.apache.org/jira/browse/HADOOP-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-13500. -- Resolution: Duplicate Already fixed by HADOOP-13556. Closing as a dup

[jira] [Resolved] (HADOOP-15208) DistCp to offer -xtrack option to save src/dest filesets as alternative to delete()

[ https://issues.apache.org/jira/browse/HADOOP-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-15208. -- Resolution: Duplicate Fix Version/s: (was: 3.1.0) > Dis

[jira] [Reopened] (HADOOP-15208) DistCp to offer -xtrack option to save src/dest filesets as alternative to delete()

[ https://issues.apache.org/jira/browse/HADOOP-15208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-15208: -- Reopening and closing this instead as a dup of HADOOP-15209 as I can't

[jira] [Resolved] (HADOOP-14974) org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation fails in trunk

[ https://issues.apache.org/jira/browse/HADOOP-14974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-14974. -- Resolution: Duplicate Fix Version/s: (was: 3.1.0

[jira] [Reopened] (HADOOP-14974) org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation fails in trunk

[ https://issues.apache.org/jira/browse/HADOOP-14974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-14974: -- HADOOP-14954 never made it to a release. And there's no other patch

[jira] [Reopened] (HADOOP-14714) handle InternalError in bulk object delete through retries

[ https://issues.apache.org/jira/browse/HADOOP-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-14714: -- Reopening and closing this instead as a dup of HADOOP-13786 as I don't

[jira] [Resolved] (HADOOP-14714) handle InternalError in bulk object delete through retries

[ https://issues.apache.org/jira/browse/HADOOP-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-14714. -- Resolution: Duplicate Fix Version/s: (was: 3.1.0) > han

[jira] [Resolved] (HADOOP-14381) S3AUtils.translateException to map 503 reponse to => throttling failure

[ https://issues.apache.org/jira/browse/HADOOP-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-14381. -- Resolution: Duplicate Fix Version/s: (was: 3.1.0

[jira] [Reopened] (HADOOP-14381) S3AUtils.translateException to map 503 reponse to => throttling failure

[ https://issues.apache.org/jira/browse/HADOOP-14381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-14381: -- Reopening and closing this instead as a dup of HADOOP-13786 as I don't

[jira] [Resolved] (HADOOP-13205) S3A to support custom retry policies; failfast on unknown host

[ https://issues.apache.org/jira/browse/HADOOP-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-13205. -- Resolution: Duplicate Fix Version/s: (was: 3.1.0) >

[jira] [Reopened] (HADOOP-13205) S3A to support custom retry policies; failfast on unknown host

[ https://issues.apache.org/jira/browse/HADOOP-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-13205: -- Reopening and closing this instead as a dup of HADOOP-13786 as I don't

[jira] [Reopened] (HADOOP-13811) s3a: getFileStatus fails with com.amazonaws.AmazonClientException: Failed to sanitize XML document destined for handler class

[ https://issues.apache.org/jira/browse/HADOOP-13811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-13811: -- Reopening and closing this instead as a dup of HADOOP-13786 as I don't

[jira] [Resolved] (HADOOP-13811) s3a: getFileStatus fails with com.amazonaws.AmazonClientException: Failed to sanitize XML document destined for handler class

[ https://issues.apache.org/jira/browse/HADOOP-13811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-13811. -- Resolution: Duplicate Fix Version/s: (was: 3.1.0) >

[jira] [Reopened] (HADOOP-14303) Review retry logic on all S3 SDK calls, implement where needed

[ https://issues.apache.org/jira/browse/HADOOP-14303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-14303: -- Reopening and closing this instead as a dup of HADOOP-13786 as I don't

[jira] [Resolved] (HADOOP-14303) Review retry logic on all S3 SDK calls, implement where needed

[ https://issues.apache.org/jira/browse/HADOOP-14303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-14303. -- Resolution: Duplicate Fix Version/s: (was: 3.1.0) > Rev

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

latest >>>>> trunk code (commit: 49c747ab187d0650143205ba57ca19607ec4c6bd). >> Since >>>>> there >>>>> are no objections, so I will go ahead to do the branch replace. >>>>> >>>>> Since we don't have force p

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

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

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

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

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

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

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

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

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

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

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 -

Re: [VOTE] Release Apache Hadoop 3.0.0 RC0

gt; issue. This problem is not reproducible with a more recent JDK 8, such as > 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

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

[jira] [Resolved] (HADOOP-15041) XInclude support in .xml configuration file is broken after "5eb7dbe9b31a45f57f2e1623aa1c9ce84a56c4d1" commit

[ https://issues.apache.org/jira/browse/HADOOP-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved HADOOP-15041. -- Resolution: Duplicate Closing instead as a duplicate. {code} commit

[jira] [Reopened] (HADOOP-15041) XInclude support in .xml configuration file is broken after "5eb7dbe9b31a45f57f2e1623aa1c9ce84a56c4d1" commit

[ https://issues.apache.org/jira/browse/HADOOP-15041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened HADOOP-15041: -- > XInclude support in .xml configuration file is broken af

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

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

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

eleases. 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.0 release and move over our focus into 3.0. Thanks +Vinod > --

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

the old 2.x release. >> * 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 &

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

ices on the new YARN UI > All these new services are optional and are sitting outside of the existing > system, 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

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

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

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: [DISCUSS] Branches and versions for Hadoop 3

+1 to Andrew’s proposal for 3.x releases. We had fairly elaborate threads on this branching & compatibility topic before. One of them’s here: [1] +1 to what Jason said. (a) Incompatible changes are not to be treated lightly. We need to stop breaking stuff and ‘just dump it on trunk'. (b)

Re: Branch merges and 3.0.0-beta1 scope

> From a release management perspective, it's *extremely* reasonable to block > the inclusion of new features a month from the planned release date. A > typical software development lifecycle includes weeks of feature freeze and > weeks of code freeze. It is no knock on any developer or any

Re: Branch merges and 3.0.0-beta1 scope

Agreed. I was very clearly not advocating for rushing in features. If you have followed my past emails, I have only strongly advocated features be worked in branches and get merged when they are in a reasonable state. Each branch contributor group should look at their readiness and merge stuff

Re: [VOTE] Merge feature branch YARN-5355 (Timeline Service v2) to trunk

worked hard and contributed towards > this effort with patches, reviews and guidance: Rohith Sharma K S, Varun > Saxena, Haibo Chen, Sangjin Lee, Li Lu, Vinod Kumar Vavilapalli, Joep > Rottinghuis, Jason Lowe, Jian He, Robert Kanter, Micheal Stack. > > Regards, > Vrushali >

Re: Branch merges and 3.0.0-beta1 scope

Steve, You can be strict & ruthless about the timelines. Anything that doesn’t get in by mid-September, as was originally planned, can move to the next release - whether it is feature work on branches or feature work on trunk. The problem I see here is that code & branches being worked on for

Re: Branch merges and 3.0.0-beta1 scope

Andrew, Each of the branches below have been created more than a year ago (!) and have been consistently worked upon and are now finally seeing the light of the day. When they are "few weeks” away, pushing them out by 7 *more* months just doesn’t make sense. While I deeply appreciate the push

Re: Apache Hadoop 2.8.2 Release Plan

effort, please refer our release wiki [2]. > > Please share thoughts if you have any. Thanks! > > Thanks, > > Junping > > [1] 2.8.2 release Blockers/Criticals: https://s.apache.org/JM5x > [2] 2.8 Release wiki: > https://cwiki.apache.org/confluence/display/HADOOP/Ha

Re: About 2.7.4 Release

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:

Re: [VOTE] Release Apache Hadoop 2.8.0 (RC2)

Thanks for taking the mantle from me on 2.8.0 and some persistent work getting 2.8.0 out the door, Junping! Apologies for bringing this up late, but I’d like to add one comment. We should repeat what we did for 2.7.0 and In line with our experience there, we should annotate this release as not

Re: [VOTE] Release Apache Hadoop 2.7.3 RC2

, 2016 at 11:55 PM, Jason Lowe <jl...@yahoo-inc.com.invalid> >> wrote: >> >>> +1 (binding) >>> - Verified signatures and digests- Successfully built from source with >>> native support- Deployed a single-node cluster- Ran some sample jobs >>> s

[jira] [Created] (HADOOP-13544) JDiff reports unncessarily show unannotated APIs and cause confusion while our javadocs only show annotated and public APIs

Vinod Kumar Vavilapalli created HADOOP-13544: Summary: JDiff reports unncessarily show unannotated APIs and cause confusion while our javadocs only show annotated and public APIs Key: HADOOP-13544 URL

[jira] [Created] (HADOOP-13543) [Umbrella] Analyse 2.8.0 and 3.0.0-alpha1 jdiff reports and fix any issues

Vinod Kumar Vavilapalli created HADOOP-13543: Summary: [Umbrella] Analyse 2.8.0 and 3.0.0-alpha1 jdiff reports and fix any issues Key: HADOOP-13543 URL: https://issues.apache.org/jira/browse/HADOOP

Re: [VOTE] Release Apache Hadoop 2.7.3 RC2

Too late for 2.7.3 - I want us to quickly get back to a regular cadence of releases. Doesn’t look like a regression IAC. Let’s put it in the next release if needed. Thanks +Vinod > On Aug 22, 2016, at 6:19 AM, Brahma Reddy Battula > wrote: > > Felt like

Re: Updated 2.8.0-SNAPSHOT artifact

Jon, That is around the time when I branched 2.8, so I guess you were getting SNAPSHOT artifacts till then from the branch-2 nightly builds. If you need it, we can set up SNAPSHOT builds. Or just wait for the first RC, which is around the corner. +Vinod > On Jul 28, 2016, at 4:27 PM,

Re: adding contributor roles timing out again

It happens to me too on both Firefox / Chrome. +Vinod > On Aug 18, 2016, at 8:39 AM, Chris Nauroth wrote: > > It’s odd that Firefox didn’t work for you. My standard workaround is to use > Firefox, and that’s what I just did successfully for shenyinjie. > > It’s

[VOTE] Release Apache Hadoop 2.7.3 RC2

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

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

in a micro release, much less a minor? >> c) Where is the release note for this change? >> >> >>> On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli <vino...@apache.org> >>> wrote: >>> >>> Hi all, >>> >>> I've created a re

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

a minor? > c) Where is the release note for this change? > > >> On Aug 12, 2016, at 9:45 AM, Vinod Kumar Vavilapalli <vino...@apache.org> >> wrote: >> >> Hi all, >> >> I've created a release candidate RC1 for Apache Hadoop 2.7.3. >> >> As

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

Thanks Steve, this is one area that isn’t very well release-tested usually! +Vinod > On Aug 16, 2016, at 2:25 AM, Steve Loughran wrote: > > I've just looked at the staged JARs and how they worked with downstream apps > —that being a key way that Hadoop artifacts are

Re: [VOTE] Release Apache Hadoop 2.7.3 RC1

/5474c9e736d4c44a603a3f6749130b67cd4da52f> > > > Thanks, > Marco > > > > 2016-08-12 18:45 GMT+02:00 Vinod Kumar Vavilapalli <vino...@apache.org > <mailto:vino...@apache.org>>: > Hi all, > > I've created a release candidate RC1 for Apache Hado

[VOTE] Release Apache Hadoop 2.7.3 RC1

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

Re: [VOTE] Release Apache Hadoop 2.7.3 RC0

But, everyone please do continue your sanity checking on RC0 in case there are more issues to be fixed. Thanks +Vinod > On Jul 26, 2016, at 12:11 PM, Vinod Kumar Vavilapalli <vino...@apache.org> > wrote: > > Thanks Daniel and Wei. > > I think these are worth fixing,

Re: [VOTE] Release Apache Hadoop 2.7.3 RC0

o:rusha...@yahoo-inc.com.invalid>> wrote: > Thanks Vinod for all the release work ! > +1 (non-binding). > * Downloaded from source and built it.* Deployed a pseudo distributed cluster. > * Ran some sample jobs: sleep, pi* Ran some dfs commands.* Everything works > fine. >

[DISCUSS] Release numbering semantics with concurrent (>2) releases [Was Setting JIRA fix versions for 3.0.0 releases]

Forking the thread to make sure it attracts enough eye-balls. The earlier one was about 3.0.0 specifically and I don’t think enough people were watching that. I’ll try to summarize a bit. # Today’s state of release numbering and ordering: So far, all the releases we have done, we have

Re: Yes/No newbie question on contributing

The short answer is that it is expected to pass without any errors. On branch-2.x, that command passes cleanly without any errors though it takes north of 10 minutes. Note that I run it with -DskipTests - you don’t want to wait for all the unit tests to run, that’ll take too much time. I expect

Re: Setting JIRA fix versions for 3.0.0 releases

+1 Thanks +Vinod > On Jul 26, 2016, at 7:39 AM, Wangda Tan wrote: > > lets try to use both jdiff and the new tool and compare results because this > is the first time with the new tool. > > Appreciate your time to help us about this effort!

Re: [Release thread] 2.8.0 release activities

ches or very stale patches. It > would be > a good exercise to come up with the list of JIRAs that we need to block > 2.8.0 for and focus our attention on closing them out. Thoughts? > > Thanks, > Sangjin > > On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran > <ste...@ho

Re: [DISCUSS] 2.6.x line releases

It wasn’t a vote. PMC doesn’t vote on code-changes. It was an extensive community discussion. We arrived at that decision to reflect the reality that not many users were running JDK6 anyways at that point of time. Sorry to bust the bubble, this is not one of those things that supports your

  1   2   3   4   >