[
https://issues.apache.org/jira/browse/HADOOP-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-4766:
--------------------------------
Description:
When I ran the gridmix 2 benchmark load on a fresh cluster of 500 nodes with
hadoop trunk,
the gridmix load, consisting of 202 map/reduce jobs of various sizes, completed
in 32 minutes.
Then I ran the same set of the jobs on the same cluster, yhey completed in 43
minutes.
When I ran them the third times, it took (almost) forever --- the job tracker
became non-responsive.
The job tracker's heap size was set to 2GB.
The cluster is configured to keep up to 500 jobs in memory.
The job tracker kept one cpu busy all the time. Look like it was due to GC.
I believe the release 0.18/0.19 have the similar behavior.
I believe 0.18 and 0.18 also have the similar behavior.
was:
When I ran the gridmix 2 benchmark load on a fresh cluster of 500 nodes with
hadoop trunk,
the gridmix load, consisting of 202 map/reduce jobs of various sizes, completed
in 32 minutes.
Then I ran the same set of the jobs on the same cluster, yhey completed in 43
minutes.
When I ran them the third times, it took (almost) forever --- the job tracker
became non-responsive.
The job tracker's heap size was set to 2GB.
The cluster is configured to keep up to 500 jobs in memory.
The job tracker kept one cpu busy all the time. Look like it was due to GC.
I believe the release 0.18/0.19 have the similar behavior.
I believe 0.18 and 0.18 also have the similar behavior.
Priority: Blocker (was: Major)
Fix Version/s: 0.20.0
0.19.1
0.18.3
Marking it a blocker for the coming releases of the versions this bug was
observed on.
> Hadoop performance degrades significantly as more and more jobs complete
> ------------------------------------------------------------------------
>
> Key: HADOOP-4766
> URL: https://issues.apache.org/jira/browse/HADOOP-4766
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.2, 0.19.0
> Reporter: Runping Qi
> Priority: Blocker
> Fix For: 0.18.3, 0.19.1, 0.20.0
>
>
> When I ran the gridmix 2 benchmark load on a fresh cluster of 500 nodes with
> hadoop trunk,
> the gridmix load, consisting of 202 map/reduce jobs of various sizes,
> completed in 32 minutes.
> Then I ran the same set of the jobs on the same cluster, yhey completed in 43
> minutes.
> When I ran them the third times, it took (almost) forever --- the job tracker
> became non-responsive.
> The job tracker's heap size was set to 2GB.
> The cluster is configured to keep up to 500 jobs in memory.
> The job tracker kept one cpu busy all the time. Look like it was due to GC.
> I believe the release 0.18/0.19 have the similar behavior.
> I believe 0.18 and 0.18 also have the similar behavior.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
