Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1248168676.1250704274835.JavaMail.jira@brutus>
Date: Wed, 19 Aug 2009 10:51:14 -0700 (PDT)
From: "Dick King (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-751) Rumen: a tool to extract job
 characterization data from job tracker logs
In-Reply-To: <1000083436.1247371514815.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-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dick King updated MAPREDUCE-751:
--------------------------------

                 Tags: rumen,mumakil,job tracker logs
        Fix Version/s: 0.21.0
                       0.20.1
    Affects Version/s: 0.21.0
                       0.20.1
               Status: Patch Available  (was: Open)

This patch implements Rumen as described by this issue.  Rumen consumes job tracker log directories and produces the job traces that mumakil and GridMMIX cosume.

> Rumen: a tool to extract job characterization data from job tracker logs
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-751
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-751
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.20.1, 0.21.0
>            Reporter: Dick King
>             Fix For: 0.20.1, 0.21.0
>
>         Attachments: 2009-08-19--1030.patch, mapreduce-751--2009-07-23.patch
>
>
>  We propose a new map/reduce component, rumen, which can be used to process job history logs to produce any or all of the following:
>       * Retrospective info describing the statistical behavior of the
> amount of time it would have taken to launch a job into a certain
> percentage of the number of mapper slots in the log's cluster, given the
> load over the period covered by the log
>       * Statistical info as to the runtimes and shuffle times, etc. of
> the tasks and jobs covered by the log
>       * files describing detailed job trace information, and the
> network topology as inferred from the host locations and rack IDs that
> arise in the job tracker log.  In addition to this facility, rumen
> includes readers for this information to return job and detailed task
> information to other tools.
>         These other tools include a more advanced version of gridmix, and also includes mumak: see blocked issues.

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