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] Commented: (HADOOP-3245) Provide ability to persist running jobs (extend HADOOP-1876)
Date Mon, 30 Jun 2008 06:31:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609163#action_12609163
] 

Amar Kamat commented on HADOOP-3245:
------------------------------------

bq. Known issues : 
4) Some job level parameters can be changed dynamically after the job is submitted e.g job
priority etc. Since it is not persisted, there is no way for the JT to load it upon restart.
Also consider the following case where the user asks the JT to kill a job and the JT crashes
before deleting the persisted structures. Upon restart the JT will continue to run the _supposed-to-be-dead_
job. Hence all such _external modifications (events)_ to the submitted job should be logged/persisted.

> 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
>
>
> 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