Re: [VOTE] Moving Submarine to a separate Apache project proposal

2019-09-02 Thread zhankun tang
+1 Thanks for Wangda's proposal. The submarine project is born within Hadoop, but not limited to Hadoop. It began with a trainer on YARN but it quickly realized that only a trainer is not enough to meet the AI platform requirements. But now there's no user-friendly open-source solution covers the

Re: [VOTE] Moving Submarine to a separate Apache project proposal

2019-09-02 Thread Xun Liu
+1 Hello everyone, I am a member of the submarine development team. I have been contributing to submarine for more than a year. I have seen the progress of submarine development very fast. In more than a year, there are 9 long-term developers of different companies. Contributing, submarine cumulat

Re: [VOTE] Moving Submarine to a separate Apache project proposal

2019-09-02 Thread Devaraj K
+1 Thanks Wangda for the proposal. I would like to participate in this project, Please add me also to the project. Regards Devaraj K On Mon, Sep 2, 2019 at 8:50 PM zac yuan wrote: > +1 > > Submarine will be a complete solution for AI service development. It can > take advantage of two best cl

Re: [VOTE] Moving Submarine to a separate Apache project proposal

2019-09-02 Thread zac yuan
+1 Submarine will be a complete solution for AI service development. It can take advantage of two best cluster systems: yarn and k8s, which will help more and more people get AI ability. To be a separate Apache project, will accelerate the procedure of development apparently. Look forward to a b

Re: [VOTE] Moving Submarine to a separate Apache project proposal

2019-09-02 Thread Naganarasimha Garla
+ 1, I would also like start participate in this project, hope to get myself added to the project. Thanks and Regards, + Naga On Tue, Sep 3, 2019 at 8:35 AM Wangda Tan wrote: > Hi Sree, > > I put it to the proposal, please let me know what you think: > > The traditional path at Apache would

Re: [DISCUSS] ARM/aarch64 support for Hadoop

2019-09-02 Thread Duo Zhang
For HBase, we purged all the protobuf related things from the public API, and then upgraded to a shaded and relocated version of protobuf. We have created a repo for this: https://github.com/apache/hbase-thirdparty But since the hadoop dependencies still pull in the protobuf 2.5 jars, our coproce

Re: [VOTE] Moving Submarine to a separate Apache project proposal

2019-09-02 Thread Wangda Tan
Hi Sree, I put it to the proposal, please let me know what you think: The traditional path at Apache would have been to create an incubator > project, but the code is already being released by Apache and most of the > developers are familiar with Apache rules and guidelines. In particular, > the

Re: [DISCUSS] ARM/aarch64 support for Hadoop

2019-09-02 Thread Anu Engineer
+1, for the branch idea. Just FYI, Your biggest problem is proving that Hadoop and the downstream projects work correctly after you upgrade core components like Protobuf. So while branching and working on a branch is easy, merging back after you upgrade some of these core components is insanely har

[jira] [Created] (YARN-9808) Zero length files in container log output haven't got a header

2019-09-02 Thread Adam Antal (Jira)
Adam Antal created YARN-9808: Summary: Zero length files in container log output haven't got a header Key: YARN-9808 URL: https://issues.apache.org/jira/browse/YARN-9808 Project: Hadoop YARN Iss

[jira] [Created] (YARN-9807) ContainerAllocator re-creates RMContainer instance when allocate for ReservedContainer

2019-09-02 Thread Yicong Cai (Jira)
Yicong Cai created YARN-9807: Summary: ContainerAllocator re-creates RMContainer instance when allocate for ReservedContainer Key: YARN-9807 URL: https://issues.apache.org/jira/browse/YARN-9807 Project: H

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

2019-09-02 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/432/ No changes -1 overall The following subsystems voted -1: asflicense compile findbugs hadolint mvnsite pathlen unit xml The following subsystems voted -1 but were configured to be filtered/ignor

[jira] [Resolved] (YARN-8139) Skip node hostname resolution when running SLS.

2019-09-02 Thread Abhishek Modi (Jira)
[ https://issues.apache.org/jira/browse/YARN-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Modi resolved YARN-8139. - Resolution: Duplicate > Skip node hostname resolution when running SLS. >