Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 96892 invoked from network); 20 Oct 2008 05:51:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Oct 2008 05:51:11 -0000 Received: (qmail 40948 invoked by uid 500); 20 Oct 2008 05:51:07 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 40902 invoked by uid 500); 20 Oct 2008 05:51:06 -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 40887 invoked by uid 99); 20 Oct 2008 05:51:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Oct 2008 22:51:06 -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; Mon, 20 Oct 2008 05:50:05 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4841C234C236 for ; Sun, 19 Oct 2008 22:50:44 -0700 (PDT) Message-ID: <15701507.1224481844294.JavaMail.jira@brutus> Date: Sun, 19 Oct 2008 22:50:44 -0700 (PDT) From: "Amar Kamat (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4428) Job Priorities are not handled properly In-Reply-To: <1597698827.1224164806405.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640927#action_12640927 ] Amar Kamat commented on HADOOP-4428: ------------------------------------ Few comments : 1) The other {{submitJob}} api in {{TestCapacityScheduler}} should call the new {{submitJob}} api with {{NORMAL}} priority. 2) {{testJobPriorities()}} : What is the need to running a large job that takes up the cluster? Wouldn't a tasktracker with just one slot suffice? Something like this {code} 1) submit 5 jobs with different priorities 2) check if they are sorted as expected 3) init the first job in the waiting queue. 4) check assignTasks() to see if no task is assigned. 5) launch setup tasks for the first job in the waiting queue 6) check assignTasks() to see if the result is as expected 7) finish the just launched task to free up the slot 8) do (5), (6) and (7) for other jobs in the waiting queue. {code} Rest of the code looks fine. > Job Priorities are not handled properly > ---------------------------------------- > > Key: HADOOP-4428 > URL: https://issues.apache.org/jira/browse/HADOOP-4428 > Project: Hadoop Core > Issue Type: Bug > Components: contrib/capacity-sched > Affects Versions: 0.19.0 > Environment: Cluster: 106 TTs MapCapacity=212, ReduceCapacity=212 > Single Queue=default, User Limit=25, Priorities = Yes. > Using hadoop branch 0.19 revision=705159 > Reporter: Karam Singh > Assignee: Vinod K V > Priority: Blocker > Fix For: 0.19.0 > > Attachments: HADOOP-4428-20081017.1.txt > > > Job Priorities are not handled properly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.