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 Mon, 15 Sep 2008 15:21:46 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.3-no-log.patch

Attaching a new patch that fixes a small bug in the previous patch. With HADOOP-3150, it was
assumed that while invoking  {{TaskInProgress.shouldCommit()}}, the variable {{taskCommit}}
is set. Upon restart, the variable remained *null* as there is no _COMMIT_PENDING_ attempt
in recovery. There used to be NPE when the tracker with _COMMIT_PENDING_ attempts (for completed
tips) tried to rejoin the jobtracker. Now {{TaskInProgress.shouldCommit()}} also checks if
the tip is complete or not. 

Ant test failed on the following test 
  - TestHighRAMJobs
  - TestMapRed
  - TestLocalJobControl
These tests failed on trunk too.

Tested this patch on 100 nodes and restart work fine.


> 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, HADOOP-3245-v5.36.1-no-log.patch,
HADOOP-3245-v5.36.2-no-log.patch, HADOOP-3245-v5.36.3-no-log.patch, HADOOP-3245-v5.36.3-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.


Mime
View raw message