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] Commented: (HADOOP-4350) Ability to pause/resume jobs
Date Wed, 08 Oct 2008 10:07:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637846#action_12637846

Devaraj Das commented on HADOOP-4350:

I agree with Owen. Offline, Amar mentioned to me that the main intention behind this issue
was to support namenode bounce (in which case the service  talked about in this jira would
be the namenode service). I can see that point. However, the thing to note here is that in
the case of namenode being unavailable, the JT itself won't be able to do anything useful
(no new jobs can be launched, new task launches trying to use the dfs would die, etc). So
if we just address the problem of JT pause (where we pause all jobs) as opposed to a single
job pause it should be enough.

> Ability to pause/resume jobs
> ----------------------------
>                 Key: HADOOP-4350
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4350
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: mapred
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>         Attachments: HADOOP-4350-v1.2.patch, HADOOP-4350-v1.3.patch
> Consider a case where the user job depends on some external entity/service like a database
or a web service. If the service needs restart or encounters a failure, the user should be
able to pause the job and resume only when the service is up. This will be better than re-executing
the whole job. Hence there should be some way to pause/resume jobs (from web-ui/command line)

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

View raw message