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

2017-08-26 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/504/ [Aug 25, 2017 2:16:17 PM] (jlowe) YARN-6640. AM heartbeat stuck when responseId overflows MAX_INT. [Aug 25, 2017 4:55:46 PM] (arp) HADOOP-14729. Upgrade JUnit 3 test cases to JUnit 4. Contributed by Ajay [

Re: [VOTE] Merge YARN-3926 (resource profile) to trunk

2017-08-26 Thread Sunil G
Hi Daniel Thank you very much for the support. * When you say that the feature can be turned off, do you mean resource types or resource profiles? I know there's an off-by-default property that governs resource profiles, but I didn't see any way to turn off resource types. Yes,*yarn.resourcemana

Re: [VOTE] Merge YARN-3926 (resource profile) to trunk

2017-08-26 Thread Sunil G
Thanks Arun for checking the feature. * can you folks point me to any test application / framework or has this been integrated with MapReduce Currently this feature is integrated with Distributed Shell. Reference: YARN-5588 This is not yet integrated with MapReduce. This work is ongoing in YARN-65

Re: [VOTE] Merge YARN-3926 (resource profile) to trunk

2017-08-26 Thread Daniel Templeton
Quick question, Wangda.  When you say that the feature can be turned off, do you mean resource types or resource profiles?  I know there's an off-by-default property that governs resource profiles, but I didn't see any way to turn off resource types.  Even if only CPU and memory are configured,

[jira] [Created] (HADOOP-14809) hadoop-aws shell profile not being built

2017-08-26 Thread Steve Loughran (JIRA)
Steve Loughran created HADOOP-14809: --- Summary: hadoop-aws shell profile not being built Key: HADOOP-14809 URL: https://issues.apache.org/jira/browse/HADOOP-14809 Project: Hadoop Common Issu

Re: hadoop 3 scripts & classpath setup

2017-08-26 Thread Steve Loughran
> On 25 Aug 2017, at 19:49, Allen Wittenauer wrote: > > >> On Aug 25, 2017, at 10:00 AM, Steve Loughran wrote: >> >> Catching up on this. Looks like I don't have a hadoop-aws profile, which >> explains a lot, doesn't it. > > Yes. This is exactly the type of failure I'd expect. > >> H