hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-1687) Stress submission policy does not always stress the cluster.
Date Sun, 01 Apr 2012 05:01:34 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amar Kamat resolved MAPREDUCE-1687.
-----------------------------------

    Resolution: Fixed

This got incorporated as part of our 0.20 to trunk forward-porting effort.
                
> Stress submission policy does not always stress the cluster.
> ------------------------------------------------------------
>
>                 Key: MAPREDUCE-1687
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1687
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/gridmix
>            Reporter: Hong Tang
>            Assignee: Amar Kamat
>         Attachments: mr-1687-yhadoop-20.1xx-20100416.patch, mr-1687-yhadoop-20.1xx-20100423-2.patch,
mr-1687-yhadoop-20.1xx-20100423.patch
>
>
> Currently, the rough idea of stress submission policy is to continue submitting jobs
until the pending map tasks reach 2x of the cluster capacity. This proves to be inadequate
and we saw a large job could monopolize the whole cluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message