hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3245) Provide ability to persist running jobs (extend HADOOP-1876)
Date Thu, 11 Sep 2008 15:53:44 GMT

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

Amar Kamat updated HADOOP-3245:

    Attachment: HADOOP-3245-v5.36-no-log.patch

Attaching a patch that incorporates Devaraj's comments. 

Changes are as follows :
1) Fixed a bug w.r.t decoding/encoding of history filenames. Earlier the filenames were pattern-matched
without decoding. 
2) Removed line delimiters. Earlier the parser used to prematurely terminate the history line
breaking the test cases. HADOOP-2304 will fix that. That was just a small hack to get this
patch working.
3) Removed the comparator used in RecoveryManager for comparing job-id. {{JobID.compareTo()}}
will suffice.
4) Fixed a bug w.r.t trimming of job names.
5) Fixed the bug in {{MiniMRCluster.setJobPriority()}} to use {{JobTracker.setJobPriority()}}
instead of {{JobInProgress.setPriority()}}.
6) Fixed a bug in RecoveryManager to do with 0 start-time. Now RecoveryManager applies job-updates
only if the updates are available. Earlier the job start-time was set to 0 if the fields were
7) Test case now has 3 separate checks 
  - job-submission-order
  - job-start-time (NEW)
  - job-finish-time
Note that I have used some code from HADOOP-4112 to do with TASK_TYPE=CLEANUP. Will fix that
once HADOOP-4112 is committed.

> Provide ability to persist running jobs (extend HADOOP-1876)
> ------------------------------------------------------------
>                 Key: HADOOP-3245
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3245
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Amar Kamat
>         Attachments: HADOOP-3245-v2.5.patch, HADOOP-3245-v2.6.5.patch, HADOOP-3245-v2.6.9.patch,
HADOOP-3245-v4.1.patch, HADOOP-3245-v5.13.patch, HADOOP-3245-v5.14.patch, HADOOP-3245-v5.26.patch,
HADOOP-3245-v5.30-nolog.patch, HADOOP-3245-v5.31.3-nolog.patch, HADOOP-3245-v5.33.1.patch,
HADOOP-3245-v5.35.3-no-log.patch, HADOOP-3245-v5.36-no-log.patch
> This could probably extend the work done in HADOOP-1876. This feature can be applied
for things like jobs being able to survive jobtracker restarts.

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

View raw message