Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 97816 invoked from network); 25 Mar 2009 04:24:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Mar 2009 04:24:14 -0000 Received: (qmail 76821 invoked by uid 500); 25 Mar 2009 04:24:12 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 76737 invoked by uid 500); 25 Mar 2009 04:24:12 -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 76661 invoked by uid 99); 25 Mar 2009 04:24:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Mar 2009 04:24:11 +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; Wed, 25 Mar 2009 04:24:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E757F234C046 for ; Tue, 24 Mar 2009 21:23:50 -0700 (PDT) Message-ID: <1087290767.1237955030946.JavaMail.jira@brutus> Date: Tue, 24 Mar 2009 21:23:50 -0700 (PDT) From: "Hemanth Yamijala (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Created: (HADOOP-5567) Add support for scheduling jobs based on memory requirements to the 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 Add support for scheduling jobs based on memory requirements to the Fairscheduler --------------------------------------------------------------------------------- Key: HADOOP-5567 URL: https://issues.apache.org/jira/browse/HADOOP-5567 Project: Hadoop Core Issue Type: New Feature Components: contrib/fair-share Reporter: Hemanth Yamijala In HADOOP-3759, we added the ability for users to specify jobs requesting for a certain amount of virtual memory. For e.g. users can say that their jobs require 2GB of memory to run. In HADOOP-4035, functionality was added to the capacity scheduler to schedule jobs based on this specified amount. This JIRA is to add similar support to the Fairshare scheduler. The basic use case is that there are jobs that require a certain known amount of virtual memory, usually more than the JVM's heap size. This happens specifically for streaming jobs that can launch several processes from the child. Without being aware of these requirements, if tasks are scheduled on nodes just based on available slots, they have a potential of affecting the other processes running on the node, or if memory protection features are enabled (HADOOP-3581), they could result in the task being killed by the tasktracker. The scheduler must take into account the requested amount of memory by the job, the amount of memory that can be committed to by a tracker, and schedule based on these inputs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.