[jira] [Created] (HDFS-13074) Ozone File System

2018-01-26 Thread Jitendra Nath Pandey (JIRA)
Jitendra Nath Pandey created HDFS-13074: --- Summary: Ozone File System Key: HDFS-13074 URL: https://issues.apache.org/jira/browse/HDFS-13074 Project: Hadoop HDFS Issue Type: New Feature

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

2018-01-26 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/669/ [Jan 25, 2018 7:36:40 PM] (weiy) HDFS-13049. RBF: Inconsistent Router OPTS config in branch-2 and [Jan 25, 2018 9:06:01 PM] (yufei) YARN-7798. Refactor SLS Reservation Creation. Contributed by Young Chen.

Re: [VOTE] Merge YARN-6592 feature branch to trunk

2018-01-26 Thread Weiwei Yang
+1 We are also looking forward to this : ) -- Weiwei On 27 Jan 2018, 9:16 AM +0800, Wangda Tan , wrote: +1 On Sat, Jan 27, 2018 at 2:05 AM, Chris Douglas mailto:cdoug...@apache.org>> wrote: +1 Looking forward to this. -C On Fri, Jan 26, 2018 at 7:28 AM, Arun Suresh mailto:asur...@apache.org>>

Re: Hadoop 3.1.0 release discussion

2018-01-26 Thread Wangda Tan
Hi All, Just a reminder about feature freeze date. Feature freeze date for 3.1.0 release is Jan 30 PST (about 4 days from today), If you've any features which live in a branch and targeted to 3.1.0, please reply this email thread. Ideally, we should finish branch merging before feature freeze dat

Re: [VOTE] Merge YARN-6592 feature branch to trunk

2018-01-26 Thread Wangda Tan
+1 On Sat, Jan 27, 2018 at 2:05 AM, Chris Douglas wrote: > +1 Looking forward to this. -C > > On Fri, Jan 26, 2018 at 7:28 AM, Arun Suresh wrote: > > Hello yarn-dev@ > > > > Based on the positive feedback from the DISCUSS thread [1], I'd like to > > start a formal vote to merge YARN-6592 [2] to

[jira] [Created] (HDFS-13073) Cleanup code in InterQJournalProtocol.proto

2018-01-26 Thread Bharat Viswanadham (JIRA)
Bharat Viswanadham created HDFS-13073: - Summary: Cleanup code in InterQJournalProtocol.proto Key: HDFS-13073 URL: https://issues.apache.org/jira/browse/HDFS-13073 Project: Hadoop HDFS Iss

[jira] [Created] (HDFS-13072) Ozone: DatanodeStateMachine: Handling Uncaught Exception in command handler thread

2018-01-26 Thread Nanda kumar (JIRA)
Nanda kumar created HDFS-13072: -- Summary: Ozone: DatanodeStateMachine: Handling Uncaught Exception in command handler thread Key: HDFS-13072 URL: https://issues.apache.org/jira/browse/HDFS-13072 Project:

[jira] [Created] (HDFS-13071) Ozone: JMX name of RocksDbMetastore should be sanitized

2018-01-26 Thread Elek, Marton (JIRA)
Elek, Marton created HDFS-13071: --- Summary: Ozone: JMX name of RocksDbMetastore should be sanitized Key: HDFS-13071 URL: https://issues.apache.org/jira/browse/HDFS-13071 Project: Hadoop HDFS Iss

[jira] [Created] (HDFS-13070) Ozone: SCM: Support for container replica reconciliation - 1

2018-01-26 Thread Nanda kumar (JIRA)
Nanda kumar created HDFS-13070: -- Summary: Ozone: SCM: Support for container replica reconciliation - 1 Key: HDFS-13070 URL: https://issues.apache.org/jira/browse/HDFS-13070 Project: Hadoop HDFS

***UNCHECKED*** Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-26 Thread Arun Suresh
Thanks everyone. I've opened a VOTE thread.. @Carlo Interesting idea to support Kubernates API. Definitely makes sense. My understanding is that we can emulate specification for a k8 POD within our scheme of things by assigning the same source tag to a set of scheduling requests. Ill dig in to thi

Re: [VOTE] Merge YARN-6592 feature branch to trunk

2018-01-26 Thread Chris Douglas
+1 Looking forward to this. -C On Fri, Jan 26, 2018 at 7:28 AM, Arun Suresh wrote: > Hello yarn-dev@ > > Based on the positive feedback from the DISCUSS thread [1], I'd like to > start a formal vote to merge YARN-6592 [2] to trunk. The vote will run for 5 > days, and will end Jan 31 7:30AM PDT. >

Re: [VOTE] Merge YARN-6592 feature branch to trunk

2018-01-26 Thread Carlo Aldo Curino
+1 On Jan 26, 2018 9:28 AM, "Sunil G" wrote: > +1 > > - Sunil > > > On Fri, Jan 26, 2018 at 8:58 PM Arun Suresh wrote: > >> Hello yarn-dev@ >> >> Based on the positive feedback from the DISCUSS thread [1], I'd like to >> start a formal vote to merge YARN-6592 [2] to trunk. The vote will run for

Re: [VOTE] Merge YARN-6592 feature branch to trunk

2018-01-26 Thread Sunil G
+1 - Sunil On Fri, Jan 26, 2018 at 8:58 PM Arun Suresh wrote: > Hello yarn-dev@ > > Based on the positive feedback from the DISCUSS thread [1], I'd like to > start a formal vote to merge YARN-6592 [2] to trunk. The vote will run for > 5 days, and will end Jan 31 7:30AM PDT. > > This feature ad

[VOTE] Merge YARN-6592 feature branch to trunk

2018-01-26 Thread Arun Suresh
Hello yarn-dev@ Based on the positive feedback from the DISCUSS thread [1], I'd like to start a formal vote to merge YARN-6592 [2] to trunk. The vote will run for 5 days, and will end Jan 31 7:30AM PDT. This feature adds support for placing containers in YARN using rich placement constraints. For

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

2018-01-26 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/116/ [Jan 24, 2018 7:19:46 PM] (jianhe) YARN-7801. AmFilterInitializer should addFilter after fill all [Jan 24, 2018 8:51:22 PM] (jlowe) MAPREDUCE-7015. Possible race condition in JHS if the job is not loaded

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-26 Thread Carlo Aldo Curino
Also I think this can help us close the gap (and surpass) Kubernetes for complex services (at least for resource management)... It would be awesome to have a compatibility layer so folks can run Kubernetes natives apps on a yarn cluster. On Jan 26, 2018 1:32 AM, "Carlo Aldo Curino" wrote: +1.

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-26 Thread Carlo Aldo Curino
+1. I didn't runs tests, but I like the design, and speaking with ops teams that operate large clusters I hear this is a feature they think is going to help a lot, so I am very supportive of this effort. On Jan 25, 2018 7:08 PM, "Konstantinos Karanasos" wrote: > Thanks for starting the thread Ar