[
https://issues.apache.org/jira/browse/HADOOP-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538678
]
Runping Qi commented on HADOOP-2119:
------------------------------------
Yes, the #running-mappers kept on going up and went beyond the actual number
of RUNNING mappers on the task trackers (which is roughly 3 * NUMBER OF TASK
TRACKERS).
The problem happened consistently, and easy (for me) to reproduce.
The job has 0 reducer, just scans through a large input data set, and the
mappers do not write anything out.
I've killed the jobtracker, thus cannot do "kill -3" anymore.
> JobTracker becomes non-responsive if the task trackers finish task too fast
> ---------------------------------------------------------------------------
>
> Key: HADOOP-2119
> URL: https://issues.apache.org/jira/browse/HADOOP-2119
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Runping Qi
> Fix For: 0.16.0
>
>
> I ran a job with 0 reducer on a cluster with 390 nodes.
> The mappers ran very fast.
> The jobtracker lacks behind on committing completed mapper tasks.
> The number of running mappers displayed on web UI getting bigger and bigger.
> The jos tracker eventually stopped responding to web UI.
> No progress is reported afterwards.
> Job tracker is running on a separate node.
> The job tracker process consumed 100% cpu, with vm size 1.01g (reach the heap
> space limit).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
