Re: [VOTE] Moving Ozone to a separated Apache project

+1 Weiwei On Friday, September 25, 2020, Dinesh Chitlangia wrote: > +1 > > Thanks, > Dinesh > > On Fri, Sep 25, 2020 at 2:00 AM Elek, Marton wrote: > > > Hi all, > > > > Thank you for all the feedback and requests, > > > > As we discussed in the previous thread(s) [1], Ozone is proposed to be

Re: [ANNOUNCE] New Apache Hadoop Committer - He Xiaoqiao

Congratulations Xiaoqiao! On Thu, Jun 11, 2020 at 11:20 AM Sree Vaddi wrote: > Congratulations, He Xiaoqiao. > > Thank you./Sree > > > > On Thursday, June 11, 2020, 9:54:32 AM PDT, Chao Sun < > sunc...@apache.org> wrote: > > Congrats Xiaoqiao! > > On Thu, Jun 11, 2020 at 9:36 AM Ayush

Re: [DISCUSS] making Ozone a separate Apache project

+1 Thanks, Marton for starting the discussion. One question, for the committers who contributed to Ozone before and got the committer-role in the past (like me), will they carry the committer-role to the new repo? On Wed, May 13, 2020 at 9:07 AM Dinesh Chitlangia wrote: > +1 > Thank you Marton

Re: [Announcement] DiDi HDFS successfully upgraded from 2.7.2 to 3.2.0

Awesome! You guys rock!! Any plan to upgrade YARN to latest version too? -- Weiwei On Dec 9, 2019, 5:20 PM -0800, Hui Fei , wrote: > Hi Eric, > > It's Rolling Upgrade without downtime. We have a cluster with thousands of > nodes and 5 namespace, it takes 1 month to do the upgrade. Upgrading >

Re: [VOTE] Release Hadoop-3.1.3-RC0

+1 (binding) - Downloaded source, setup a single node cluster - Verified basic HDFS operations, put/get/cat etc - Verified basic YARN restful apis, cluster/nodes/scheduler, all seem good - Run several distributed shell job Thanks Weiwei On Sep 19, 2019, 4:28 PM +0800, Sunil Govindan , wrote: >

Re: [VOTE] Release Apache Hadoop 3.2.1 - RC0

+1 (binding) Downloaded tarball, setup a pseudo cluster manually Verified basic HDFS operations, copy/view files Verified basic YARN operations, run sample DS jobs Verified basic YARN restful APIs, e.g cluster/nodes info etc Set and verified YARN node-attributes, including CLI Thanks Weiwei On

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

+1 (binding) Thanks Weiwei On Wed, Sep 18, 2019 at 6:35 AM Wangda Tan wrote: > +1 (binding). > > From my experiences of Submarine project, I think moving to a separate repo > helps. > > - Wangda > > On Tue, Sep 17, 2019 at 11:41 AM Subru Krishnan wrote: > > > +1 (binding). > > > > IIUC, there

Re: [VOTE] Move Submarine source code, documentation, etc. to a separate Apache Git repo

+1 Thanks Weiwei On Aug 27, 2019, 9:40 AM +0800, Xun Liu , wrote: > +1 (non-binding) > This is the best news. > > Peter Bacsko 于2019年8月27日周二 上午4:59写道： > > > +1 (non-binding) > > > > On Sat, Aug 24, 2019 at 4:06 AM Wangda Tan wrote: > > > > > Hi devs, > > > > > > This is a voting thread to move

Re: Aug Hadoop Community Meetup in China

Hi Junping Thanks. I would like to get a slot to talk about our new open source project: YuniKorn. Thanks Weiwei On Jul 23, 2019, 5:08 PM +0800, 俊平堵 , wrote: > Thanks for these positive feedbacks! The local community has voted the date > and location to be 8/10, Beijing. So please book your

Re: Aug Hadoop Community Meetup in China

Hi Junping Thanks for organizing this event ! Just finished the survey, looking forward to meet folks in the coming meet up. Thanks Weiwei On Jul 18, 2019, 3:28 PM +0800, 俊平堵 , wrote: > Hi, all! > > I am glad to let you know that we are organizing > Hadoop Contributors Meetup in China on Aug. >

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

Thanks Marton, +1 on this. Weiwei On Jul 17, 2019, 2:07 PM +0800, 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 >

[ANNOUNCE] New Apache Hadoop Committer - Tao Yang

Hi Dear Apache Hadoop Community It's my pleasure to announce that Tao Yang has been elected as an Apache Hadoop committer, this is to recognize his contributions to Apache Hadoop YARN project. Congratulations and welcome on board! Weiwei (On behalf of the Apache Hadoop PMC)

Re: Agenda & More Information about Hadoop Community Meetup @ Palo Alto, June 26

Thanks Wangda. Will this event be recorded? It will be extremely helpful for people who are unable to join to catch up. Thanks Weiwei On Jun 26, 2019, 4:12 AM +0800, Wangda Tan , wrote: A friendly reminder, The meetup will take place tomorrow at 9:00 AM PDT to 4:00 PM PDT. The address is: 395

Re: [VOTE] Release Apache Hadoop Submarine 0.2.0 - RC0

+1 (binding) Thanks Weiwei On Jun 21, 2019, 5:33 AM +0800, Wangda Tan , wrote: +1 Binding. Tested in local cluster and reviewed docs. Thanks! On Wed, Jun 19, 2019 at 3:20 AM Sunil Govindan wrote: +1 binding - tested in local cluster. - tried tony run time as well - doc seems fine now. -

Re: Apache Hadoop 3.1.1 release plan

Hi Wangda I would propose to have https://issues.apache.org/jira/browse/YARN-8015 included in 3.1.1. Once this is done, we get both intra and inter placement constraint covered so users could start to explore this feature. Otherwise the functionality is pretty limited. It has been Patch

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

Hi Wangda +1 (non-binding) - Smoke tests with teragen/terasort/DS jobs - Various of metrics, UI displays validation, compatible tests - Tested GPU resource-type - Verified RM fail-over, app-recovery - Verified 2 threads async-scheduling - Enabled placement constraints, tested

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

Hi Wangda While testing the build, we found a bug https://issues.apache.org/jira/browse/YARN-8085, it might cause NPE during RM fail-over. I think that needs to be included in 3.1.0. We have run some other tests, and they look good so far. This includes - Some basic teragen/terasort/DS jobs -

Re: [NOTICE] branch-3.1 created. 3.1.0 code freeze started.

Hi Wangda I am a bit confused about the branches, I am expecting something like following  branch-3.1.0: 3.1.0  branch-3.1: 3.1.x  trunk: 3.2.x Code freezes in branch-3.1.0 which only allows blocks. However, did you mean you created branch-3.1 for 3.1.0? In this case, what branch should be

Re: [ANNOUNCE] Apache Hadoop 3.0.0 GA is released

Hi Andrew Congratulations on the 3.0 GA, another mile stone of Hadoop history. Thanks for driving this release, excellent work! Took a look at the release notes, also seems nice. But one question, who is maintaining https://wiki.apache.org/hadoop/PoweredBy? Some of info is quite out of date,

Re: [VOTE] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

+1 (non-binding) Thanks for getting this done Sunil. -- Weiwei On 5 Dec 2017, 4:06 AM +0800, Eric Payne , wrote: +1. Thanks Sunil for the work on this branch. Eric From: Sunil G ;

Re: [DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

Hi Sunil +1 from my side. Actually we have applied some of these patches to our production cluster since Sep this year, on over 2000+ nodes and it works nicely. +1 for the merge. I am pretty sure this feature will help a lot of users, especially those on cloud. Thanks for getting this done,

Re: Apache Hadoop 2.8.3 Release Plan

Agree with Konstantin. This two issues has been opened for a while but could not reach a consensus on the fix, hope this gets enough attention from the community and get them resolved. Thanks -- Weiwei On 22 Nov 2017, 11:18 AM +0800, Konstantin Shvachko , wrote: I would

[jira] [Resolved] (MAPREDUCE-6847) Job history server should release jobs from cache after a fixed duration

[ https://issues.apache.org/jira/browse/MAPREDUCE-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved MAPREDUCE-6847. Resolution: Won't Fix > Job history server should release jobs from cache after a fi

[jira] [Created] (MAPREDUCE-6847) Job history server should release jobs from cache after a fixed duration

Weiwei Yang created MAPREDUCE-6847: -- Summary: Job history server should release jobs from cache after a fixed duration Key: MAPREDUCE-6847 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6847

[jira] [Created] (MAPREDUCE-6762) ControlledJob#toString failed with NPE when job status is not successfully updated

Weiwei Yang created MAPREDUCE-6762: -- Summary: ControlledJob#toString failed with NPE when job status is not successfully updated Key: MAPREDUCE-6762 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6762

[jira] [Resolved] (MAPREDUCE-6185) YARN M/R may return NaN for reducer progress after Job completion

[ https://issues.apache.org/jira/browse/MAPREDUCE-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved MAPREDUCE-6185. Resolution: Cannot Reproduce YARN M/R may return NaN for reducer progress after Job