hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Gummadi (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3597) Provide a way to access other info of history file from Rumentool
Date Fri, 23 Dec 2011 09:52:30 GMT

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

Ravi Gummadi updated MAPREDUCE-3597:

    Attachment: 3597.v0.patch

Attaching a patch that adds API for accessing the other info (which is not writtent to trace
> Provide a way to access other info of history file from Rumentool
> -----------------------------------------------------------------
>                 Key: MAPREDUCE-3597
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3597
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: tools/rumen
>    Affects Versions: 0.24.0
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>             Fix For: 0.24.0
>         Attachments: 3597.v0.patch
> As the trace file generated by Rumen TraceBuilder is skipping some of the info like job
counters, task counters, etc. we need a way to access "other info available in history file
which is not dumped to trace file". This is useful for components which want to parse history
files and get info. These components can directly use/leverage "Rumen's parsing of history
files across hadoop releases" and get history info in a consistent way for further analysis/processing.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message