hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5004) 'job -kill' from command line should inform if the job doesn't exist
Date Mon, 12 Jan 2009 11:43:59 GMT

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

Steve Loughran commented on HADOOP-5004:
----------------------------------------

we'd need JobTracker.killJob() to return something other than void() in such a situation,
or throw a subclass of IOException. 

Having the client look for the job and failing if it is not there would leave open a race
condition.

> 'job -kill' from command line should inform if the job doesn't exist
> --------------------------------------------------------------------
>
>                 Key: HADOOP-5004
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5004
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.21.0
>            Reporter: Amar Kamat
>             Fix For: 0.21.0
>
>
> Killing an invalid job from command line succeeds with a message stating "job killed".


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