[
https://issues.apache.org/jira/browse/HADOOP-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643945#action_12643945
]
Vinod K V commented on HADOOP-4444:
-----------------------------------
All these issues seem to be bugs(but not, as established by now) because of two
different sources - scheduler's own structures and the cluster-summary. Even
after doing what is done in the latest patch, we still will find the
discrepancies because JIP.runningTasks is updated immediately after giving away
new tasks but not when it is actually running (i.e when removed from
expireLaunchingTasks list).
After discussing this with Hemanth, realized that at the place where we
actually use these counts (in the scheduler) we do *have* the correct values.
We are anyway going to remove these counts from the scheduler UI (HADOOP-4445)
as they are already displayed in cluster-summary. Once we fix HADOOP-4445,
these issues will no longer be visible.
> Scheduling Information for queues shows one map/reduce task less then actual
> running map/reduce tasks.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4444
> URL: https://issues.apache.org/jira/browse/HADOOP-4444
> 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-4444-1.patch, HADOOP-4444.patch
>
>
> Scheduling Information for queues shows one map/reduce task less then actual
> running map/reduce tasks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
