You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ravi Gummadi (JIRA)" <ji...@apache.org> on 2010/10/18 07:19:23 UTC

[jira] Updated: (MAPREDUCE-2137) Mapping between Gridmix jobs and the corresponding original MR jobs is needed

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

Ravi Gummadi updated MAPREDUCE-2137:
------------------------------------

    Attachment: 2137.patch

Attaching patch for trunk with the above mentioned changes.

Testcase changes are not fully testing the main code change of this patch(i.e. gridmix job name change) as the testcases are exercising MockJob instead of ZombieJob.

> 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.22.0
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>             Fix For: 0.22.0
>
>         Attachments: 2137.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.
-
You can reply to this email to add a comment to the issue online.