hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3008) [Gridmix] Improve cumulative CPU usage emulation for short running tasks
Date Wed, 05 Oct 2011 09:37:34 GMT

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

Amar Kamat updated MAPREDUCE-3008:
----------------------------------

    Attachment: mapreduce-2591-v1.7.patch

Attaching a new patch incorporating Ravi's offline comments. 

test-patch passed:
{noformat}
+1 overall.  

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit
warnings.
{noformat}

All the JUnit tests in test-contrib passed except TestUserResolve, which is a known issue
(MAPREDUCE-2950).
                
> [Gridmix] Improve cumulative CPU usage emulation for short running tasks
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3008
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3008
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: contrib/gridmix
>    Affects Versions: 0.24.0
>            Reporter: Amar Kamat
>              Labels: cpu-emulation, gridmix
>             Fix For: 0.24.0
>
>         Attachments: mapreduce-2591-v1.4.2.patch, mapreduce-2591-v1.7.patch
>
>
> CPU emulation in Gridmix fails to meet the expected target if the map has no data to
sort/spill/merge. There are 2 major reasons for this:
> 1. The map task end immediately ends soon after the map task. The map progress is 67%
while the map phase ends. 
> 2. Currently, the sort (comparator) doesnt emulate CPU. If the map is short lived, the
CPU emulation thread (spawned from the map task in cleanup) doesn't get a chance to emulate.

--
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