[
https://issues.apache.org/jira/browse/HADOOP-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635949#action_12635949
]
Vinod K V commented on HADOOP-4287:
-----------------------------------
After running through the logs, I've realized that the negative count on
running tasks results because of TTs that report failed tasks *after* the job
is killed due to maximum TIP failures being hit. A killed job resets its
running tasks count to zero, any task failures reported, after the job is
marked as killed, bring down the count to a negative value. Don't know for
sure, but I guess we should not update task-status of jobs that are already
marked succeeded/failed/killed.
> [mapred] jobqueue_details.jsp shows negative count of running and waiting
> reduces with CapacityTaskScheduler.
> -------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4287
> URL: https://issues.apache.org/jira/browse/HADOOP-4287
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Vinod K V
> Assignee: Sreekanth Ramakrishnan
> Priority: Blocker
>
> This I observed while running a job that always fails because of reduce
> failures. Need to investigate this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
