[
https://issues.apache.org/jira/browse/MAPREDUCE-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Gummadi updated MAPREDUCE-2137:
------------------------------------
Fix Version/s: 0.23.0
Affects Version/s: (was: 0.22.0)
0.23.0
Release Note: New configuration properties gridmix.job.original-job-id
and gridmix.job.original-job-name in the configuration of simulated job are
exposed/documented to gridmix user for mapping between original cluster's jobs
and simulated jobs.
Status: Patch Available (was: Open)
> 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
