hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3771) JobClient.runJob() should not kill the job on IOExceptions
Date Mon, 21 Jul 2008 07:51:31 GMT

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

dhruba borthakur commented on HADOOP-3771:

This feature will be really useful in clusters that have long-running JobTrackers. 

There are times when we have to restart the JT. HADOOP-3245 gives us the flexibility of restarting
the JT anytime without losing any currently submitted jobs. But the entire story is complete
only if new job-submissions do not error out when the JT is restarting. This JIRA will be
immensely helpful if it can make the JobClient aware of JT restarts and not fail a new job

> JobClient.runJob() should not kill the job on IOExceptions
> ----------------------------------------------------------
>                 Key: HADOOP-3771
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3771
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
> Currently the {{JobClient.runJob()}} submits a job to the job tracker and then periodically
asks the JT for the job's progress. On successive IOExceptions the JobClient kills the job.
This is not a desired behaviour since the JobClient is issuing a kill-job command to the JT
which is not reachable. This is a problem for HADOOP-3245 since its highly possible that the
JT can come up anytime and then it makes no sense to kill the job.

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

View raw message