Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 55367 invoked from network); 28 Nov 2010 05:24:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Nov 2010 05:24:06 -0000 Received: (qmail 12961 invoked by uid 500); 28 Nov 2010 05:24:06 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 12847 invoked by uid 500); 28 Nov 2010 05:24:06 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 12839 invoked by uid 99); 28 Nov 2010 05:24:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Nov 2010 05:24:05 +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.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Nov 2010 05:24:03 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAS5Nf8A020325 for ; Sun, 28 Nov 2010 05:23:41 GMT Message-ID: <29283568.4291290921821860.JavaMail.jira@thor> Date: Sun, 28 Nov 2010 00:23:41 -0500 (EST) From: "Arun C Murthy (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-2108) Allow TaskScheduler manage number slots on TaskTrackers 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/MAPREDUCE-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964498#action_12964498 ] Arun C Murthy commented on MAPREDUCE-2108: ------------------------------------------ Can you please describe the changes you are making here... > Allow TaskScheduler manage number slots on TaskTrackers > ------------------------------------------------------- > > Key: MAPREDUCE-2108 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2108 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: contrib/capacity-sched, contrib/fair-share > Affects Versions: 0.22.0 > Reporter: Scott Chen > Assignee: Scott Chen > Fix For: 0.22.0 > > Attachments: MAPREDUCE-2108.txt > > > Currently the map slots and reduce slots are managed by TaskTracker configuration. > To change the task tracker slots, we need to restart the TaskTrackers. > Also, for a non-uniform cluster, we have to deploy different sets of configuration. > Now JobTracker holds the CPU and memory status of TaskTrackers (MAPREDUCE-1218). > So it makes sense to just let JobTracker.taskScheduler decided the number of slots on each node. > This way we can > 1. Change the number of slots dynamically without restarting TaskTracker > 2. Use different number of slots based on the resource of a TaskTracker > To achieve this, we need to change the logic that we use totalMapSlots and totalReduceSlots in JobTracker. > I think they are used in WebUI and speculativeCap. > We will need to make JobTracker calculate these numbers from TaskScheduler and TaskTrackerStatus. > TaskScheduler and TaskTracker can both hold their maximum slots. We pick the smaller one. > Thoughts? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.