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

I'm adding my +1 (binding) to conclude the vote. With 13 +1's (11 binding) and no -1's, the vote passes. We'll get on with the merge to trunk shortly. Thanks everyone! Regards Vrushali On Tue, Aug 29, 2017 at 10:54 AM, varunsax...@apache.org < varun.saxena.apa...@gmail.com> wrote: > +1

Re: Apache Hadoop 2.8.2 Release Plan

Thanks Brahma for comment on this thread. To be clear, I always update branch version just before RC kicking off. For 2.8.2 release, I don't have plan to involve big top or other third-party test tools. As always, we will rely on test/verify efforts from community especially from large

Re: [DISCUSS] Branches and versions for Hadoop 3

Hi Andrew, We have completed the merge of TSv2 to trunk. You can now go ahead with the branching. Regards, Varun Saxena. On Tue, Aug 29, 2017 at 11:35 PM, Andrew Wang wrote: > Sure. Ping me when the TSv2 goes in, and I can take care of branching. > > We're still

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/508/ [Aug 29, 2017 11:21:14 AM] (sunilg) YARN-6386. Show decommissioning nodes in new YARN UI. Contributed by [Aug 29, 2017 11:36:22 AM] (aajisaka) HADOOP-14671. Upgrade to Apache Yetus 0.5.0. [Aug 29, 2017

[jira] [Created] (MAPREDUCE-6948) TestJobImpl.testUnusableNodeTransition failed

Haibo Chen created MAPREDUCE-6948: - Summary: TestJobImpl.testUnusableNodeTransition failed Key: MAPREDUCE-6948 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6948 Project: Hadoop Map/Reduce

[jira] [Resolved] (MAPREDUCE-6949) yarn.app.mapreduce.am.log.level is not documented in mapred-default.xml

[ https://issues.apache.org/jira/browse/MAPREDUCE-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen resolved MAPREDUCE-6949. --- Resolution: Duplicate > yarn.app.mapreduce.am.log.level is not documented in

[jira] [Created] (MAPREDUCE-6949) yarn.app.mapreduce.am.log.level is not documented in mapred-default.xml

Haibo Chen created MAPREDUCE-6949: - Summary: yarn.app.mapreduce.am.log.level is not documented in mapred-default.xml Key: MAPREDUCE-6949 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6949

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

I'd have assumed it would have gone in as one single patch, rather than a full history. I don't see why the trunk needs all the evolutionary history of a build. What should our policy/process be here? I do currently plan to merge the s3guard in as one single squashed patch; just getting

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

Thanks Sangjin for the link to the previous discussions on this! I think that helps answer Steve's questions. As decided on that thread [1], YARN-5355 as a feature branch was merged to trunk via "git merge --no-ff" . Although trunk already had TSv2 code (alpha1) prior to this merge, we chose to

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

The "git" way of doing things would be to rebase the feature branch on master (trunk) and then commit the patch stack. Squashing the entire feature into a 10 MB megapatch is the "svn" way of doing things. The svn workflow evolved because merging feature branches back to trunk was really painful

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

I recall this discussion about a couple of years ago: https://lists.apache.org/thread.html/43cd65c6b6c3c0e8ac2b3c76afd9eff1f78b177fabe9c4a96d9b3d0b@1440189889@%3Ccommon-dev.hadoop.apache.org%3E On Wed, Aug 30, 2017 at 2:32 PM, Steve Loughran wrote: > I'd have assumed it