hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4191) Add a testcase for jobhistory
Date Fri, 13 Feb 2009 08:39:59 GMT

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

Devaraj Das updated HADOOP-4191:

    Fix Version/s: 0.21.0
           Status: Open  (was: Patch Available)

Some comments:
1) The Listener should check the format of the TaskID, TaskAttemptID, JobID strings (just
doing id.forName()) is sufficient).
2) We should also catch the case where END statement comes before the START (if this happens
in a real jobhistory file, the recovery manager will panic).
3) We should check for duplicates (like multiple START or END lines for the same subject)
and catch them.
4) It would be nice to capture checks for the sequence of history lines when a TT running
this job's tasks is lost.

> Add a testcase for jobhistory
> -----------------------------
>                 Key: HADOOP-4191
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4191
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred, test
>            Reporter: Amar Kamat
>            Assignee: Ravi Gummadi
>             Fix For: 0.21.0
>         Attachments: HADOOP-4191.patch, HADOOP-4191.v2.patch, HADOOP-4191.v3.patch
> Changes in job history might break the history parser which in turn might break some
features like jobtracker-recovery, history-viewer etc. There should be a testcase that catches
these incompatible changes early and informs about the expected change.

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

View raw message