[
https://issues.apache.org/jira/browse/HADOOP-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545284
]
Christian Kunz commented on HADOOP-2119:
----------------------------------------
I ran into a similar problem:
100,000 mappers with a single reducer on a 1400 node cluster with 2 tasks per
node. All the waves of mappers finished in 2 hours, but are stuck in
COMMIT_PENDING. Jobtracker is using 100% cpu (but distributed across 4 cpu's)
and seems to take 3-4 secs yo process a completed task, such that the job will
finish in about 100 hours.
Thread dump attached
> 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.
