[jira] [Updated] (MAPREDUCE-2640) The maxRunningTasks property of the LimitTasksPerJob scheduler is ambiguous in its description, and must be updated

2012-01-09 Thread Harsh J (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-2640:
---

   Resolution: Not A Problem
Fix Version/s: (was: 0.24.0)
   Status: Resolved  (was: Patch Available)

No longer a problem in MR2. I guess we can close this.

 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
  Labels: doc
 Attachments: 0.22-MAPREDUCE-2640.r1.diff, 
 0.23-MAPREDUCE-2640.r1.diff, MAPREDUCE-2640.r1.diff


 The property's entry in mapred-default.xml is like so:
 {code}
 property
   namemapreduce.jobtracker.taskscheduler.maxrunningtasks.perjob/name
   value/value
   descriptionThe 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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (MAPREDUCE-2640) The maxRunningTasks property of the LimitTasksPerJob scheduler is ambiguous in its description, and must be updated

2011-09-03 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-2640:
---

Status: Patch Available  (was: Open)

 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
  Labels: doc
 Fix For: 0.23.0

 Attachments: 0.22-MAPREDUCE-2640.r1.diff, 
 0.23-MAPREDUCE-2640.r1.diff, MAPREDUCE-2640.r1.diff


 The property's entry in mapred-default.xml is like so:
 {code}
 property
   namemapreduce.jobtracker.taskscheduler.maxrunningtasks.perjob/name
   value/value
   descriptionThe 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




[jira] [Updated] (MAPREDUCE-2640) The maxRunningTasks property of the LimitTasksPerJob scheduler is ambiguous in its description, and must be updated

2011-09-03 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/MAPREDUCE-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J updated MAPREDUCE-2640:
---

Attachment: MAPREDUCE-2640.r1.diff
0.23-MAPREDUCE-2640.r1.diff
0.22-MAPREDUCE-2640.r1.diff

Patches for trunk, 0.23, 0.22 that deprecates the misleading property and 
provides a more relevant, new one.

 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
  Labels: doc
 Fix For: 0.23.0

 Attachments: 0.22-MAPREDUCE-2640.r1.diff, 
 0.23-MAPREDUCE-2640.r1.diff, MAPREDUCE-2640.r1.diff


 The property's entry in mapred-default.xml is like so:
 {code}
 property
   namemapreduce.jobtracker.taskscheduler.maxrunningtasks.perjob/name
   value/value
   descriptionThe 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