You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2008/08/22 14:34:47 UTC

[jira] Commented: (HADOOP-3771) JobClient.runJob() should not kill the job on IOExceptions

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

Hudson commented on HADOOP-3771:
--------------------------------

Integrated in Hadoop-trunk #581 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])

> 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
>            Assignee: 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.