Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3A9D5DA28 for ; Tue, 4 Sep 2012 21:30:09 +0000 (UTC) Received: (qmail 37968 invoked by uid 500); 4 Sep 2012 21:30:09 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 37940 invoked by uid 500); 4 Sep 2012 21:30:09 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 37931 invoked by uid 99); 4 Sep 2012 21:30:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Sep 2012 21:30:09 +0000 Date: Wed, 5 Sep 2012 08:30:09 +1100 (NCT) From: "Hadoop QA (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: <935744666.35035.1346794209157.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (YARN-80) Support delay scheduling for node locality in MR2's capacity scheduler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448077#comment-13448077 ] Hadoop QA commented on YARN-80: ------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12543531/YARN-80.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The javadoc tool did not generate any warning messages. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestLeafQueue +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/18//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/18//console This message is automatically generated. > Support delay scheduling for node locality in MR2's capacity scheduler > ---------------------------------------------------------------------- > > Key: YARN-80 > URL: https://issues.apache.org/jira/browse/YARN-80 > Project: Hadoop YARN > Issue Type: Improvement > Components: capacityscheduler > Reporter: Todd Lipcon > Assignee: Arun C Murthy > Fix For: 2.1.0-alpha > > Attachments: YARN-80.patch > > > The capacity scheduler in MR2 doesn't support delay scheduling for achieving node-level locality. So, jobs exhibit poor data locality even if they have good rack locality. Especially on clusters where disk throughput is much better than network capacity, this hurts overall job performance. We should optionally support node-level delay scheduling heuristics similar to what the fair scheduler implements in MR1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira