Return-Path: 
 <mapreduce-dev-return-3732-apmail-hadoop-mapreduce-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 76E7A6017
	for <apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org>;
 Mon,  4 Jul 2011 06:46:21 +0000 (UTC)
Received: (qmail 64153 invoked by uid 500); 4 Jul 2011 06:46:19 -0000
Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org
Received: (qmail 63321 invoked by uid 500); 4 Jul 2011 06:45:53 -0000
Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-dev@hadoop.apache.org>
List-Id: <mapreduce-dev.hadoop.apache.org>
Reply-To: mapreduce-dev@hadoop.apache.org
Delivered-To: mailing list mapreduce-dev@hadoop.apache.org
Received: (qmail 61514 invoked by uid 99); 4 Jul 2011 06:45:45 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 06:45:45 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2011 06:45:43 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id BF2B344466F
	for <mapreduce-dev@hadoop.apache.org>; Mon,  4 Jul 2011 06:45:22 +0000 (UTC)
Date: Mon, 4 Jul 2011 06:45:22 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: 
 <1741159332.1402.1309761922779.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (MAPREDUCE-2640) The maxRunningTasks property of
 the LimitTasksPerJob scheduler is ambiguous in its description, and must be
 updated
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

The maxRunningTasks property of the LimitTasksPerJob scheduler is ambiguous in its description, and must be updated
-------------------------------------------------------------------------------------------------------------------

                 Key: MAPREDUCE-2640
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2640
             Project: Hadoop Map/Reduce
          Issue Type: Task
          Components: documentation
    Affects Versions: 0.20.2
            Reporter: Harsh J
            Assignee: Harsh J
             Fix For: 0.23.0


The property's entry in mapred-default.xml is like so:

{code}
<property>
  <name>mapreduce.jobtracker.taskscheduler.maxrunningtasks.perjob</name>
  <value></value>
  <description>The maximum number of running tasks for a job before
  it gets preempted. No limits if undefined.
  </description>
</property>
{code}

There is no mention that this is a property exclusive to the LimitTasksPerJob scheduler alone. The doc ought to be updated to note that unless there's a plan of reusing such a property (I do not see fair or capacity schedulers utilizing this, and they use their own configs).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira