[
https://issues.apache.org/jira/browse/MAPREDUCE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007654#comment-13007654
]
Matei Zaharia commented on MAPREDUCE-486:
-----------------------------------------
The thing is that they don't actually take a slot from the point of view of the
scheduler: the JobTracker will launch new tasks in the same slot that a
commit-pending task is in. Thus, you may end up with more tasks listed as
"running" than you have slots.
> JobTracker web UI counts COMMIT_PENDING tasks as Running
> --------------------------------------------------------
>
> Key: MAPREDUCE-486
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-486
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Todd Lipcon
> Assignee: Harsh J Chouraria
> Priority: Minor
>
> In jobdetails.jsp, tasks in COMMIT_PENDING state are listed as "Running". I
> propose creating another column in this table for COMMIT_PENDING tasks, since
> users find it confusing that a given job can have more tasks "Running" than
> their total cluster capacity.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
