[DISCUSS] ARM/aarch64 support for Hadoop

Hi Folks, ARM is becoming famous lately in its processing capability and has got the potential to run Bigdata workloads. Many users have been moving to ARM machines due to its low cost. In the past there were attempts to compile Hadoop on ARM (Rasberry PI) for experimental purposes. Today ARM

Re: [VOTE] Merge YARN-8200 to branch-2 and branch-3.0

+1 (non-binding). I have built branch-2 with the latest YARN-8200 patch (YARN-8200-branch-2.003.patch). I ran all of the NM/RM tests and ran a few test jobs on a one-node cluster with default settings. On Mon, Aug 26, 2019 at 3:51 PM Oliver Hu wrote: > +1 (non-binding) > > We have used this

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

+1 (non-binding) On Sat, Aug 24, 2019 at 4:06 AM Wangda Tan wrote: > Hi devs, > > This is a voting thread to move Submarine source code, documentation from > Hadoop repo to a separate Apache Git repo. Which is based on discussions of > >

Re: [VOTE] Merge YARN-8200 to branch-2 and branch-3.0

+1 (binding) As Jonathan said this feature in branch-2 has been running stably for over a year. Therefore I’m supportive to the merge On Mon, Aug 26, 2019 at 2:00 PM Jim Brennan wrote: > +1 (non-binding). > I have built branch-2 with the latest YARN-8200 patch > (YARN-8200-branch-2.003.patch).

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: [VOTE] Move Submarine source code, documentation, etc. to a separate Apache Git repo

+1 - Sunil On Sat, Aug 24, 2019 at 7:36 AM Wangda Tan wrote: > Hi devs, > > This is a voting thread to move Submarine source code, documentation from > Hadoop repo to a separate Apache Git repo. Which is based on discussions of > >

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

+1 -Ayush > On 26-Aug-2019, at 9:45 PM, Bharat Viswanadham > wrote: > > +1 (non-binding) > > Thanks, > Bharat > > On Mon, Aug 26, 2019 at 9:13 AM Sean Busbey > wrote: > >> +1 (non-binding) >> >>> On Fri, Aug 23, 2019 at 9:06 PM Wangda Tan wrote: >>> >>> Hi devs, >>> >>> This is a

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

+1 given the scope of the future of Submarine, I think that makes sense. I am also happy to see Hadoop contributors being able to commit to Submarine repo. I think that'll help grow the Submarine community in the long run. On Mon, Aug 26, 2019 at 9:26 AM Ayush Saxena wrote: > +1 > > -Ayush > >

[DISCUSS] Hadoop 2.10.0 release plan

Hi folks, As discussed previously (e.g. [1], [2]) we'd like to do a 2.10.0 release soon. Some features/big-items we're targeting for this release: - YARN resource types/GPU support (YARN-8200 ) - Selective wire encryption (HDFS-13541

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

+1 (non-binding) Thanks, Wanqiang Ji On Sat, Aug 24, 2019 at 10:06 AM Wangda Tan wrote: > Hi devs, > > This is a voting thread to move Submarine source code, documentation from > Hadoop repo to a separate Apache Git repo. Which is based on discussions of > >

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

+1 (non-binding) -Dinesh On Mon, Aug 26, 2019 at 11:42 AM Wanqiang Ji wrote: > +1 (non-binding) > > Thanks, > Wanqiang Ji > > On Sat, Aug 24, 2019 at 10:06 AM Wangda Tan wrote: > > > Hi devs, > > > > This is a voting thread to move Submarine source code, documentation from > > Hadoop repo

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

+1 On Sat, Aug 24, 2019 at 3:06 AM Wangda Tan wrote: > Hi devs, > > This is a voting thread to move Submarine source code, documentation from > Hadoop repo to a separate Apache Git repo. Which is based on discussions of > >

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

On Sat, Aug 24, 2019 at 2:25 AM Wangda Tan wrote: > Hi Steve, > > The proposal is to EOL for the following branches: > > [2.0.x - 2.7.x] > [3.0.x] > > 2.8.x, 2.9.x, 2.10.x (not released yet), 3.1.x (and later) are not EOL. > one final 2.8.x, 1+ for 2.9, and then we have to start thinking 2.10

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

- Stuff has been going into branch-2 sporadically but I don't who is actively using that code other than as part of a cherrypick backwards strategy. - Should we do a 2.10.x release? Or just say "time to upgrade?" We have talked at a few different Hadoop contributors meetups and community syncs

Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/425/ No changes [Error replacing 'FILE' - Workspace is not accessible] - To unsubscribe, e-mail:

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

+1 (non-binding) On Fri, Aug 23, 2019 at 9:06 PM Wangda Tan wrote: > > Hi devs, > > This is a voting thread to move Submarine source code, documentation from > Hadoop repo to a separate Apache Git repo. Which is based on discussions of >

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

On Mon, Aug 26, 2019 at 9:20 AM Eric Badger wrote: > > - Stuff has been going into branch-2 sporadically but I don't who is > actively > using that code other than as part of a cherrypick backwards strategy. > > - Should we do a 2.10.x release? Or just say "time to upgrade?" > > We have talked at

Re: [VOTE] Mark 2.6, 2.7, 3.0 release lines EOL

This is starting to diverge from the original topic :) But I would like to say (1) If we are treating branch-2/2.0 as the final, last 2.x release, we should be proactive in updating dependencies. I did a quick search and found a lot of dependencies in branch-2 are very old, and some are even