Re: [VOTE] Merge yarn-native-services branch into trunk

+1 (binding) Tested the branch code and brought up services like sleep and httpd. Also verified UI as well. - Sunil On Tue, Oct 31, 2017 at 1:36 AM Jian He wrote: > Hi All, > > I would like to restart the vote for merging yarn-native-services to trunk. > Since last

Re: [VOTE] Merge yarn-native-services branch into trunk

+1 (binding) for branch merge. I couldn’t get the patch to work properly though. Yarn-native-services branch works fine. If bugs surface in trunk, we will fix it. Regards, Eric On 11/3/17, 2:45 PM, "Wangda Tan" wrote: Thanks all for the great works! +1

[DISCUSS] A final minor release off branch-2?

Hi all, With 3.0.0 GA around the corner (tx for the push, Andrew!), 2.9.0 RC out (tx Arun / Subru!) and 2.8.2 (tx Junping!), I think it's high time we have a discussion on how we manage our developmental bandwidth between 2.x line and 3.x lines. Once 3.0 GA goes out, we will have two parallel

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

Hey Vinod, I've cleaned up the RC directory as you requested. Cheers -Arun On Fri, Nov 3, 2017 at 4:09 PM, Vinod Kumar Vavilapalli wrote: > Arun / Subru, > > Thanks for the great work! > > Few quick comments > - Can you cleanup the RC folder to only have tar.gz and

Re: Cutting branch-2.9

Hello Junping Thanks for taking the time/effort to go through this. Including our reply so that folks in the list have the full context. > 1. It looks like we change from log4j to sel4j (HADOOP-12956) in 2.9 which is a huge incompatible change. Do we have consensus on this in community (as I saw

Re: Cutting branch-2.9

Below is some findings from my recently run of JACC (https://builds.apache.org/job/Hadoop-2.9-JACC/12/artifact/target/compat-check/report.html) job against 2.9 and 2.8.2. I have discussed with Arun and Subru offline on jdiff report who convinced me some of items are not a big concern. Just

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

Arun / Subru, Thanks for the great work! Few quick comments - Can you cleanup the RC folder to only have tar.gz and src.tar.gz and their signatures and delete everything else? So that it's easy to pick up the important bits for the voters. For e.g, like this

[VOTE] Release Apache Hadoop 2.9.0 (RC0)

Hi folks, Apache Hadoop 2.9.0 is the first stable release of Hadoop 2.9 line and will be the latest stable/production release for Apache Hadoop - it includes 30 New Features with 500+ subtasks, 407 Improvements, 787 Bug fixes new fixed issues since 2.8.2 . More information about the

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

> At a minimum, it should at least be using it’s own maven module for a > lot of the bits that generates it’s own maven jars so that we can split this > functionality up at build/test time. I expected this to be the case, but looks like it isn't. There's lot of value in splitting the

Re: [VOTE] Merge yarn-native-services branch into trunk

Thanks all for the great works! +1 (Binding). Tried to use native services to build and run applications successfully. - Wangda On Fri, Nov 3, 2017 at 11:50 AM, Arun Suresh wrote: > +1 (binding) > > Cheers > -Arun > > On Nov 3, 2017 11:44 AM, "Chandni Singh"

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

Hi folks! Thank you for sharing the design docs and the tremendous amount of work that has gone into Ozone. I'm grateful that atleast someone is trying to drastically improve HDFS. *If* there is a meeting to discuss this merge, could I please also be invited? Have we ever thought about

[jira] [Created] (YARN-7442) [YARN-7069] Limit format of resource type name

Wangda Tan created YARN-7442: Summary: [YARN-7069] Limit format of resource type name Key: YARN-7442 URL: https://issues.apache.org/jira/browse/YARN-7442 Project: Hadoop YARN Issue Type:

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

Konstantine, Thanks for your comments, questions and feedback. I have attached a document to the HDFS-7240 jira that explains a design for scaling HDFS and how Ozone paves the way towards the full solution.

[jira] [Created] (YARN-7441) Support placement policy in yarn service

Jian He created YARN-7441: - Summary: Support placement policy in yarn service Key: YARN-7441 URL: https://issues.apache.org/jira/browse/YARN-7441 Project: Hadoop YARN Issue Type: Sub-task

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

> On Nov 3, 2017, at 12:08 PM, Stack wrote: > > On Sat, Oct 28, 2017 at 2:00 PM, Konstantin Shvachko > wrote: > >> It is an interesting question whether Ozone should be a part of Hadoop. > > I don't see a direct answer to this question. Is there one?

[jira] [Created] (YARN-7440) When AM recovers, if the service record doesn’t exist for a container sent from RM, it can re-query the container status from NM instead of releasing the container

Chandni Singh created YARN-7440: --- Summary: When AM recovers, if the service record doesn’t exist for a container sent from RM, it can re-query the container status from NM instead of releasing the container Key: YARN-7440

Re: 答复: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

Hi Lei, Thank you for your interest in Ozone. Let me answer each of the specific questions. > As the current state of Ozone implementation, what are the major > benefits of using today’s Ozone over HDFS? Scale - HDFS tops out at 500/700 million keys; Ozone primary use case is to go beyond

Re: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

On Sat, Oct 28, 2017 at 2:00 PM, Konstantin Shvachko wrote: > Hey guys, > > It is an interesting question whether Ozone should be a part of Hadoop. > I don't see a direct answer to this question. Is there one? Pardon me if I've not seen it but I'm interested in the

Re: [VOTE] Merge yarn-native-services branch into trunk

+1 (binding) Cheers -Arun On Nov 3, 2017 11:44 AM, "Chandni Singh" wrote: > +1 > Thanks, > Chandni > > From: Jian He > Sent: Monday, October 30, 2017 1:49 PM > To: yarn-dev@hadoop.apache.org; Hdfs-dev;

Re: [VOTE] Merge yarn-native-services branch into trunk

+1 Thanks, Chandni From: Jian He Sent: Monday, October 30, 2017 1:49 PM To: yarn-dev@hadoop.apache.org; Hdfs-dev; Hadoop Common; mapreduce-...@hadoop.apache.org Subject: Re: [VOTE] Merge yarn-native-services branch into trunk Few

[jira] [Created] (YARN-7439) Minor improvements to Reservation System documentation/exceptions

Carlo Curino created YARN-7439: -- Summary: Minor improvements to Reservation System documentation/exceptions Key: YARN-7439 URL: https://issues.apache.org/jira/browse/YARN-7439 Project: Hadoop YARN

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/579/ [Nov 3, 2017 12:15:33 AM] (Arun Suresh) HADOOP-15013. Fix ResourceEstimator findbugs issues. (asuresh) [Nov 3, 2017 12:39:23 AM] (subru) YARN-7432. Fix DominantResourceFairnessPolicy serializable findbugs

[jira] [Created] (YARN-7438) Additional changes to make SchedulingPlacementSet agnostic to ResourceRequest / placement algorithm

Wangda Tan created YARN-7438: Summary: Additional changes to make SchedulingPlacementSet agnostic to ResourceRequest / placement algorithm Key: YARN-7438 URL: https://issues.apache.org/jira/browse/YARN-7438

[jira] [Created] (YARN-7437) Give SchedulingPlacementSet to a better name.

Wangda Tan created YARN-7437: Summary: Give SchedulingPlacementSet to a better name. Key: YARN-7437 URL: https://issues.apache.org/jira/browse/YARN-7437 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Resolved] (YARN-7426) Interrupt does not work when LocalizerRunner is reading from InputStream

[ https://issues.apache.org/jira/browse/YARN-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billie Rinaldi resolved YARN-7426. -- Resolution: Duplicate > Interrupt does not work when LocalizerRunner is reading from InputStream

[jira] [Resolved] (YARN-5908) Add affinity/anti-affinity field to ResourceRequest API

[ https://issues.apache.org/jira/browse/YARN-5908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-5908. -- Resolution: Duplicate Duplicated to YARN-6952 > Add affinity/anti-affinity field to ResourceRequest API

[jira] [Created] (YARN-7436) YARN UI: Upgrade to the latest em-table

Sreenath Somarajapuram created YARN-7436: Summary: YARN UI: Upgrade to the latest em-table Key: YARN-7436 URL: https://issues.apache.org/jira/browse/YARN-7436 Project: Hadoop YARN

Re: Cutting branch-2.9

Quick update folks. We just cut branch-2.9.0, and set the mvn version to 2.9.0 We've also updated the version on branch-2.9 to 2.9.1-SNAPSHOT. Expect an RC in the next 24 hrs :) Cheers -Arun/Subru On Tue, Oct 31, 2017 at 5:24 PM, Arun Suresh wrote: > Hi Junping, > > >

Re: 答复: [DISCUSSION] Merging HDFS-7240 Object Store (Ozone) to trunk

Hey, Weiwei and Jitendra Thanks a lot for this large effort to bring us ozone. * As the current state of Ozone implementation, what are the major benefits of using today’s Ozone over HDFS? Giving that its missing features like HDFS-12680 and HDFS-12697, being disabled by default, and the