Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <608356583.112441262912934438.JavaMail.jira@brutus.apache.org>
Date: Fri, 8 Jan 2010 01:08:54 +0000 (UTC)
From: "Chris Douglas (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-1295) We need a job trace manipulator to
 build gridmix runs.
In-Reply-To: <581949206.1260838098362.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Douglas updated MAPREDUCE-1295:
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.22.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

+1

I committed this. Thanks, Dick!

> We need a job trace manipulator to build gridmix runs.
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-1295
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1295
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>            Reporter: Dick King
>            Assignee: Dick King
>             Fix For: 0.22.0
>
>         Attachments: mapreduce-1295--2009-12-17.patch, mapreduce-1295--2009-12-21.patch, mapreduce-1295--2009-12-22.patch, mapreduce-1295--2009-12-23.patch, mapreduce-1297--2009-12-14.patch
>
>
> Rumen produces "job traces", which are JSON format files describing important aspects of all jobs that are run [successfully or not] on a hadoop map/reduce cluster.  There are two packages under development that will consume these trace files and produce actions in that cluster or another cluster: gridmix3 [see jira MAPREDUCE-1124 ] and Mumak [a simulator -- see MAPREDUCE-728 ].
> It would be useful to be able to do two things with job traces, so we can run experiments using these two tools: change the duration, and change the density.  I would like to provide a "folder", a tool that can wrap a long-duration execution trace to redistribute its jobs over a shorter interval, and also change the density by duplicating or culling away jobs from the folded combined job trace.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.