[
https://issues.apache.org/jira/browse/HADOOP-4445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-4445:
-------------------------------------------
Attachment: HADOOP-4445-1.patch
Attaching a patch fixing this issue:
The patch does the following:
1. in SchedulingInfo.toString() it does JobQueueManager.getRunningJobs(queue)
and iterates thro' running job list and keeps adding number of running tasks in
the queue. We need not worry about the jobs which are initialized but not
scheduled as those jobs would have running maps and reduces as zero.
2. Modified testSchedulingInfo() by assigning a map and reduce task to the
tracker and check the number of running tasks. Then finished the job and
checked the same. Then check for case where running job fails.
I have moved the comment from within testSchedulingInfo() to outside. I have
removed the FakeJobInProgress.fail() and I am using
taskTrackerManager.finalizeJob api instead as the latter raises events which is
required for cleaning up the running job queues.
> Wrong number of running map/reduce tasks are displayed in queue information.
> ----------------------------------------------------------------------------
>
> Key: HADOOP-4445
> URL: https://issues.apache.org/jira/browse/HADOOP-4445
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Environment: Hadoop r705159, Queue=default, GC=100%
> MapCapacity=ReduceCapacity=212
> Reporter: Karam Singh
> Assignee: Sreekanth Ramakrishnan
> Attachments: HADOOP-4445-1.patch
>
>
> Wrong number of running map/reduce tasks are displayed in queue information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
