Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 99912 invoked from network); 20 Mar 2009 15:29:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Mar 2009 15:29:13 -0000 Received: (qmail 43680 invoked by uid 500); 20 Mar 2009 15:29:11 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 43638 invoked by uid 500); 20 Mar 2009 15:29:11 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 43625 invoked by uid 99); 20 Mar 2009 15:29:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Mar 2009 08:29:11 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Mar 2009 15:29:10 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7E24B234C003 for ; Fri, 20 Mar 2009 08:28:50 -0700 (PDT) Message-ID: <810496160.1237562930502.JavaMail.jira@brutus> Date: Fri, 20 Mar 2009 08:28:50 -0700 (PDT) From: "Hadoop QA (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4788) Set mapred.fairscheduler.assignmultiple to true by default In-Reply-To: <2022982449.1228509164187.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683908#action_12683908 ] Hadoop QA commented on HADOOP-4788: ----------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12402612/hadoop-4788-v0.patch against trunk revision 756352. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 Eclipse classpath. The patch retains Eclipse classpath integrity. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/113/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/113/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/113/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/113/console This message is automatically generated. > Set mapred.fairscheduler.assignmultiple to true by default > ---------------------------------------------------------- > > Key: HADOOP-4788 > URL: https://issues.apache.org/jira/browse/HADOOP-4788 > Project: Hadoop Core > Issue Type: Improvement > Components: contrib/fair-share > Reporter: Matei Zaharia > Assignee: Matei Zaharia > Priority: Trivial > Attachments: hadoop-4788-v0.patch > > > Pretty much all users of the fair scheduler are using the "assignmultiple" feature which lets it launch reduce tasks at the same time as map tasks (on the same heartbeats), leading to reduces starting faster. This is also going to happen in Hadoop by default in HADOOP-3136. So we should set it to true by default and perhaps even remove the config parameter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.