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-3771) JobClient.runJob() should not kill the job on IOExceptions
Date Mon, 21 Jul 2008 08:41:31 GMT

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

Amar Kamat commented on HADOOP-3771:

bq. This JIRA will be immensely helpful if it can make the JobClient aware of JT restarts
and not fail a new job submission.
I think HADOOP-3618 is related to this. JobClient should keep on retrying until the JobTracker
is ready. Its probably ok not to reveal that the JobTracker is _re-starting_ / _initializing_.

> 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