Re: [DISCUSS] Making submarine to different release model like Ozone

2019-01-31 Thread Sunil G
+1 from me on this. ML/DL is one of the fast growing areas and a runtime on YARN helps customers to have ML/DL workloads to run on same cluster where the ETL or other traditional big data workloads ingest or mine data. Faster release cadence can pace up the development for Submarine and more agile

Re: [DISCUSS] Making submarine to different release model like Ozone

2019-01-31 Thread Rohith Sharma K S
+1, Few interested ML/DL folks from Banglore asked about Submarine release for trying out TensorFlow on YARN. We told them wait for release since they were not ready to use trunk. I see agile release cycle for Submarine brings lot of added value. -Rohith Sharma K S On Fri, 1 Feb 2019 at 00:34, Wa

Re: [DISCUSS] Making submarine to different release model like Ozone

2019-01-31 Thread Arun Suresh
Thanks for bringing this up Wangda. +1 Makes a lot of sense to have Submarine follow its own release cadence - for all the reasons you outlined. I would one up this proposal to ask why shouldn't we allow YARN to have its own releases as well - but that is for a separate thread :) Cheers -Arun On

Re: [DISCUSS] Making submarine to different release model like Ozone

2019-01-31 Thread Jonathan Hung
+1. This is important for improving the deep learning on hadoop story. There's recently a lot of momentum for this, and decoupling submarine/hadoop will help it continue. Jonathan Hung On Thu, Jan 31, 2019 at 11:04 AM Wangda Tan wrote: > Hi devs, > > Since we started submarine-related effort l

[DISCUSS] Making submarine to different release model like Ozone

2019-01-31 Thread Wangda Tan
Hi devs, Since we started submarine-related effort last year, we received a lot of feedbacks, several companies (such as Netease, China Mobile, etc.) are trying to deploy Submarine to their Hadoop cluster along with big data workloads. Linkedin also has big interests to contribute a Submarine Ton

Re: proposed new repository for hadoop/ozone docker images (+update on docker works)

2019-01-31 Thread Elek, Marton
Hi Eric, Thanks for the answers 1. > Hadoop-docker-ozone.git source tree naming seems to create a unique process for Ozone. Not at all. We would like to follow the existing practice which is established in HADOOP-14898. In HDDS-851 we discussed why we need two separated repositories for hadoo

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

2019-01-31 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1033/ [Jan 30, 2019 2:29:56 AM] (aajisaka) HADOOP-14178. Move Mockito up to version 2.23.4. Contributed by Akira [Jan 30, 2019 5:56:28 AM] (yqlin) HDDS-1024. Handle DeleteContainerCommand in the [Jan 30, 2019 1

[jira] [Created] (MAPREDUCE-7180) Relaunching Failed Containers

2019-01-31 Thread BELUGA BEHR (JIRA)
BELUGA BEHR created MAPREDUCE-7180: -- Summary: Relaunching Failed Containers Key: MAPREDUCE-7180 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7180 Project: Hadoop Map/Reduce Issue Typ

[jira] [Created] (MAPREDUCE-7179) Job status not available when job finished

2019-01-31 Thread Zhaohui Xin (JIRA)
Zhaohui Xin created MAPREDUCE-7179: -- Summary: Job status not available when job finished Key: MAPREDUCE-7179 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7179 Project: Hadoop Map/Reduce