[jira] [Created] (MAPREDUCE-6809) Create ContainerRequestor interface and refactor RMContainerRequestor to use it

2016-11-07 Thread Devaraj K (JIRA)
Devaraj K created MAPREDUCE-6809: Summary: Create ContainerRequestor interface and refactor RMContainerRequestor to use it Key: MAPREDUCE-6809 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6809

[jira] [Created] (MAPREDUCE-6808) Log map attempts as part of shuffle handler audit log

2016-11-07 Thread Jonathan Eagles (JIRA)
Jonathan Eagles created MAPREDUCE-6808: -- Summary: Log map attempts as part of shuffle handler audit log Key: MAPREDUCE-6808 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6808 Project: Hadoo

Re: Updated 2.8.0-SNAPSHOT artifact

2016-11-07 Thread Sangjin Lee
+1. Resetting the 2.8 effort and the branch at this point may be counter-productive. IMO we should focus on resolving the remaining blockers and getting it out the door. I also think that we should seriously consider 2.9 as well, as a fairly large number of changes have accumulated in branch-2 (ove

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

2016-11-07 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/218/ [Nov 6, 2016 9:13:31 PM] (wangda) YARN-4733. [YARN-3368] Initial commit of new YARN web UI. (wangda) [Nov 6, 2016 9:13:31 PM] (wangda) YARN-4517. Add nodes page and fix bunch of license issues. (Varun Saxe

Re: Updated 2.8.0-SNAPSHOT artifact

2016-11-07 Thread Steve Loughran
> On 4 Nov 2016, at 22:38, Jason Lowe wrote: > > At this point my preference would be to do the most expeditious thing to > release 2.8, whether that's sticking with the branch-2.8 we have today or > re-cutting it on branch-2. Doing a quick JIRA query, there's been almost > 2,400 JIRAs resol