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: Cluster Submit Applications API accepts any random ApplicationId

This is an old but known issue. I tried to search for JIRAs where we discussed this but couldn't easily. We have so far only dealt with mistake by well behaved clients, not bad users/clients. YARN-1545 was filed for some of this, but never reached fruition. It will definitely have an impact if

[jira] [Created] (YARN-9548) [Umbrella] Make YARN work well in elastic cloud environments

Vinod Kumar Vavilapalli created YARN-9548: - Summary: [Umbrella] Make YARN work well in elastic cloud environments Key: YARN-9548 URL: https://issues.apache.org/jira/browse/YARN-9548 Project

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: Cannot kill Pre-Commit jenkins builds

al/Jenkins), looks like my > id needs to be added to the hudson-jobadmin group to affect any changes on > jenkins. > But wondering why it was revoked in the first place. > > On Tue, Jan 22, 2019 at 4:21 PM Vinod Kumar Vavilapalli > wrote: > >> Minus private. &

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: Cannot kill Pre-Commit jenkins builds

Minus private. Which specific job you are looking? I looked at https://builds.apache.org/job/PreCommit-YARN-Build/ but can't seem to find any user specific auth. +Vinod > On Jan 22, 2019, at 10:00 AM, Arun Suresh wrote: > > Hey Vinod..

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

Re: Merge branch commit in trunk by mistake

What is broken due to this merge commit? +Vinod > On Jul 5, 2018, at 2:03 PM, Arun Suresh wrote: > > I agree with Sean, to be honest.. it is disruptive. > Also, we have to kind of lock down the repo till it is completed.. > > I recommend we be careful and try not to get into this situation

[jira] [Created] (YARN-8338) TimelineService V1.5 doesn't come up after HADOOP-15406

Vinod Kumar Vavilapalli created YARN-8338: - Summary: TimelineService V1.5 doesn't come up after HADOOP-15406 Key: YARN-8338 URL: https://issues.apache.org/jira/browse/YARN-8338 Project: Hadoop

[jira] [Created] (YARN-8319) More YARN pages need to honor yarn.resourcemanager.display.per-user-apps

Vinod Kumar Vavilapalli created YARN-8319: - Summary: More YARN pages need to honor yarn.resourcemanager.display.per-user-apps Key: YARN-8319 URL: https://issues.apache.org/jira/browse/YARN-8319

[jira] [Resolved] (YARN-8181) Docker container run_time

[ https://issues.apache.org/jira/browse/YARN-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-8181. --- Resolution: Invalid [~sajavadi], please see http://hadoop.apache.org

[jira] [Resolved] (YARN-7212) [Atsv2] TimelineSchemaCreator fails to create flowrun table causes RegionServer down!

[ https://issues.apache.org/jira/browse/YARN-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-7212. --- Resolution: Duplicate > [Atsv2] TimelineSchemaCreator fails to create flow

[jira] [Resolved] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1489. --- Resolution: Fixed Assignee: (was: Vinod Kumar Vavilapalli) Resolved

[jira] [Resolved] (YARN-5881) Enable configuration of queue capacity in terms of absolute resources

[ https://issues.apache.org/jira/browse/YARN-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-5881. --- Resolution: Fixed > Enable configuration of queue capacity in te

[jira] [Resolved] (YARN-6223) [Umbrella] Natively support GPU configuration/discovery/scheduling/isolation on YARN

[ https://issues.apache.org/jira/browse/YARN-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-6223. --- Resolution: Fixed > [Umbrella] Natively support GPU configuration/discov

[jira] [Resolved] (YARN-5983) [Umbrella] Support for FPGA as a Resource in YARN

[ https://issues.apache.org/jira/browse/YARN-5983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-5983. --- Resolution: Fixed > [Umbrella] Support for FPGA as a Resource in Y

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-dev@hadoop.apache.org > <mailto:yarn-dev@hadoop.apache.org>" <yarn-dev@hadoop.apache.org > <mailto:yarn-dev@hadoop.apache.org>>, Hdfs-dev <hdfs-...@hadoop.apache.org > <mailto:hdfs-...@hadoop.apache.org>>, Hadoop Common > <commo

[jira] [Resolved] (YARN-8109) Resource Manager WebApps fails to start due to ConcurrentModificationException

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

[jira] [Resolved] (YARN-7873) Revert YARN-6078

[ https://issues.apache.org/jira/browse/YARN-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-7873. --- Resolution: Fixed Fix Version/s: 3.0.1 2.9.1

[jira] [Resolved] (YARN-7064) Use cgroup to get container resource utilization

[ https://issues.apache.org/jira/browse/YARN-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-7064. --- Resolution: Fixed Resolving as Fixed instead of Done per our conventions

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: Apache YARN Committers & Contributors Meetup #5

Thanks for that update, Sunil! Good to hear that we had such a successful meet-up in Bangalore! Hoping we get back to a regular cadence! Is it worth doing a simple blog post on this at https://blogs.apache.org/hadoop/ , may be with pics etc? Plus Daniel

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

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

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: [DISCUSS] Apache YARN committers/contribu­t­ors meetup #5

t;>What we're doing with the 2.x branch going forward >>>Docker status/plans >>>Other? >>> >>>Thanks! >>>Daniel >>> >>>On 10/20/17 1:54 PM, Daniel Templeton wrote: >>>> Seems to me like we're du

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

[jira] [Created] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

Vinod Kumar Vavilapalli created YARN-6930: - Summary: Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager Key: YARN-6930 URL: https://issues.apache.org/jira/browse

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:

[jira] [Resolved] (YARN-6543) yarn application's privilege is determined by yarn process creator instead of yarn application user.

[ https://issues.apache.org/jira/browse/YARN-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-6543. --- Resolution: Not A Bug Agree with [~rohithsharma], this is working as designed

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: Queries on YARN

Hi Sabiya, > 1. Can we define our custom logical resources in YARN other than Memory & > cpu core? Is this flexibility there? There is an ongoing effort to satisfy this very requirement - you can follow https://issues.apache.org/jira/browse/YARN-3926

Re: About 2.7.4 Release

I was planning to take this up, celebrating my return from my paternity leave of absence for quite a while. Marton, let me know if you do want to take this up instead and we can work together. Thanks +Vinod > On Mar 7, 2017, at 9:13 AM, Sangjin Lee wrote: > > If we have a

[jira] [Resolved] (YARN-5068) Expose scheduler queue to application master

[ https://issues.apache.org/jira/browse/YARN-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-5068. --- Resolution: Duplicate Closing this accurately as a dup of YARN-1623. > Exp

[jira] [Resolved] (YARN-5759) Capability to register for a notification/callback on the expiry of timeouts

[ https://issues.apache.org/jira/browse/YARN-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-5759. --- Resolution: Duplicate Agree with [~rohithsharma]. Closing this as a dup

Re: Apache YARN committers/contribu­t­ors meetup #4 (10/27)

Thanks to everyone who joined this meetup! We had quite a blast both in the western hemisphere and from what I hear in the IST timezone too. Overall, stats - PST — Started at 269 patch-available tickets and got it down to 170 - a mix of commits, reviews + updates, closing invalid /

[jira] [Resolved] (YARN-3755) Log the command of launching containers

[ https://issues.apache.org/jira/browse/YARN-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-3755. --- Resolution: Duplicate Actually I think this is a dup of YARN-4309 which now

[jira] [Resolved] (YARN-2981) DockerContainerExecutor must support a Cluster-wide default Docker image

[ https://issues.apache.org/jira/browse/YARN-2981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-2981. --- Resolution: Won't Fix Agreed. I am closing this as "WON'T FIX" for

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] [Resolved] (YARN-1763) Handle RM failovers during the submitApplication call.

[ https://issues.apache.org/jira/browse/YARN-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1763. --- Resolution: Duplicate > Handle RM failovers during the submitApplication c

[jira] [Resolved] (YARN-1836) Add retry cache support in ResourceManager

[ https://issues.apache.org/jira/browse/YARN-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1836. --- Resolution: Invalid Old JIRA. As [~xgong] [mentioned on YARN-1521|https

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

[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: 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: Setting JIRA fix versions for 3.0.0 releases

Please don’t do this for 2.8.0 against 2.7.0 till we change our existing release ordering conventions. Till now, I made sure 2.8.0 only has issues that are not in 2.7.3 - per the 2.8.0-follows-2.7.3 convention. As part of the release process, I will fix the remaining tickets to follow this

Re: Setting JIRA fix versions for 3.0.0 releases

>> There's a plan for more 3.0.0 alphas, so there's still time to help out > before things settle down for beta. If 2.8.0 is ready to go, it should > happen before even alpha2. I wasn’t talk about my irresistible urge to help (which of course is there : )) , it was about making sure enough

Re: Setting JIRA fix versions for 3.0.0 releases

, this won’t do much good. Whenever we start working towards switching to this tool, it should incorporate the same exclude-annotations logic that the jdiff code-path does today. Do you think that is possible? Thanks +Vinod > On Jul 22, 2016, at 4:53 PM, Vinod Kumar Vavilapalli <vino...@apac

[VOTE] Release Apache Hadoop 2.7.3 RC0

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

  1   2   3   4   5   6   >