Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 4079 invoked from network); 10 Aug 2009 09:00:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Aug 2009 09:00:32 -0000 Received: (qmail 94024 invoked by uid 500); 10 Aug 2009 09:00:39 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 94001 invoked by uid 500); 10 Aug 2009 09:00:39 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 93991 invoked by uid 99); 10 Aug 2009 09:00:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 09:00:39 +0000 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; Mon, 10 Aug 2009 09:00:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 07B74234C04C for ; Mon, 10 Aug 2009 02:00:15 -0700 (PDT) Message-ID: <1354386720.1249894815030.JavaMail.jira@brutus> Date: Mon, 10 Aug 2009 02:00:15 -0700 (PDT) From: "Anjali M (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Created: (HADOOP-6183) improvement in fairscheduler 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 improvement in fairscheduler ---------------------------- Key: HADOOP-6183 URL: https://issues.apache.org/jira/browse/HADOOP-6183 Project: Hadoop Common Issue Type: Improvement Components: contrib/hod Affects Versions: 0.19.1 Environment: Fedora9 Reporter: Anjali M Priority: Minor I understand the hadoop fair scheduler does the scheduling at a task level. I think in the pool of jobs if we can queue up the jobs based on a backfilling strategy, the delay which long jobs might face in the current strategy, can be reduced fruther. Has anybody tried such a strategy? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.