hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2137) Mapping between Gridmix jobs and the corresponding original MR jobs is needed
Date Thu, 26 May 2011 11:39:47 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039651#comment-13039651
] 

Amar Kamat commented on MAPREDUCE-2137:
---------------------------------------

The latest patch looks good to me. +1. We can commit this.

> Mapping between Gridmix jobs and the corresponding original MR jobs is needed
> -----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2137
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2137
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/gridmix
>    Affects Versions: 0.23.0
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>             Fix For: 0.23.0
>
>         Attachments: 2137.patch, 2137.v1.patch, 2137.v2.1.patch
>
>
> Consider a trace file "trace1" obtained by running Rumen on a set of MR jobs' history
logs. When gridmix runs simulated jobs from "trace1", it may skip some of the jobs from the
trace file for some reason like out-of-order-jobs. Now use Rumen to generate trace2 from the
history logs of gridmix's simulated jobs.
> Now, to compare and analyze the gridmix's simulated jobs with original MR jobs, we need
a mapping between them.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message