You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Nishan Shetty (JIRA)" <ji...@apache.org> on 2012/07/12 11:23:34 UTC
[jira] [Created] (MAPREDUCE-4431) killing already completed
application gives ambiguous message as "Application has been killed"
Nishan Shetty created MAPREDUCE-4431:
----------------------------------------
Summary: killing already completed application gives ambiguous message as "Application has been killed"
Key: MAPREDUCE-4431
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Reporter: Nishan Shetty
Priority: Minor
If we try to kill the already completed application by the following command it gives ambiguous message as "Application has been killed"
./mapred job -kill <already completed application id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418118#comment-13418118 ]
Hadoop QA commented on MAPREDUCE-4431:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12537135/MAPREDUCE-4431-1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test files.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2624//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2624//console
This message is automatically generated.
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417185#comment-13417185 ]
Harsh J commented on MAPREDUCE-4431:
------------------------------------
Thanks Devaraj. Couple of points:
* In case of a job -kill on killed, failed or succeeded jobs, given your patch, we'll get a very ambiguous: "Could not kill the Job since the Job State is {KILLED,FAILED,SUCCEEDED}.".
** Perhaps we can instead check for state better and say things in each case thats more apt/intelligible.
*** "Could not kill the job <job ID>, as it has already succeeded."
*** "Could not mark the job <job ID> as killed, as it has already failed."
*** "The job <job ID> has already been killed."
* Can we have a test for this? That is, if we're trying to prevent a double killJob() calls to the AM/cluster.
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Mayank Bansal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428273#comment-13428273 ]
Mayank Bansal commented on MAPREDUCE-4431:
------------------------------------------
+1 Looks good.
Thanks,
Mayank
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428590#comment-13428590 ]
Harsh J commented on MAPREDUCE-4431:
------------------------------------
bq. In case the job was already killed, should we perhaps return 0 exitCode (since the kill was (already) successful?
On second thought, lets not do this, as it would be in violation of what a command's run means. Only if the command were truly successful for that very instance we should return 0. So +1 and committing shortly.
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Devaraj K (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj K updated MAPREDUCE-4431:
---------------------------------
Status: Patch Available (was: Open)
Updated the patch with review comments fix, Please review it.
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Devaraj K (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj K updated MAPREDUCE-4431:
---------------------------------
Assignee: Devaraj K
Affects Version/s: 3.0.0
2.0.0-alpha
Status: Patch Available (was: Open)
Attaching the patch to fix this ambiguity issue.
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Devaraj K (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj K updated MAPREDUCE-4431:
---------------------------------
Attachment: MAPREDUCE-4431.patch
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Priority: Minor
> Attachments: MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Nishan Shetty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412635#comment-13412635 ]
Nishan Shetty commented on MAPREDUCE-4431:
------------------------------------------
{noformat}
12/07/12 14:27:35 INFO mapred.ClientServiceDelegate: Application state is completed. FinalApplicationStatus=SUCCEEDED. Redirecting to job history server
12/07/12 14:27:35 INFO mapred.ResourceMgrDelegate: Killing application application_1342080430464_0001
Killed job job_1342080430464_0001
{noformat}
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Nishan Shetty
> Priority: Minor
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Devaraj K (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj K updated MAPREDUCE-4431:
---------------------------------
Status: Open (was: Patch Available)
Thanks a lot Harsh for looking into the patch.
Cancelling patch to address Harsh comments.
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428541#comment-13428541 ]
Harsh J commented on MAPREDUCE-4431:
------------------------------------
+1, looks good to me too.
One comment though (just want your thought):
{code}
+ System.out.println("The job " + jobid + " has already been killed.");
+ exitCode = -1;
{code}
In case the job was already killed, should we perhaps return 0 exitCode (since the kill was (already) successful?
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417029#comment-13417029 ]
Hadoop QA commented on MAPREDUCE-4431:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12536978/MAPREDUCE-4431.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2621//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2621//console
This message is automatically generated.
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Devaraj K (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj K updated MAPREDUCE-4431:
---------------------------------
Attachment: MAPREDUCE-4431-1.patch
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Nishan Shetty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nishan Shetty updated MAPREDUCE-4431:
-------------------------------------
Description:
If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
./mapred job -kill <already completed job id>
was:
If we try to kill the already completed application by the following command it gives ambiguous message as "Application has been killed"
./mapred job -kill <already completed application id>
Summary: killing already completed job gives ambiguous message as "Killed job <job id>" (was: killing already completed application gives ambiguous message as "Application has been killed")
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Nishan Shetty
> Priority: Minor
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Devaraj K (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427989#comment-13427989 ]
Devaraj K commented on MAPREDUCE-4431:
--------------------------------------
Hi Harsh, can you have a look into the updated patch when you find some time?
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4431) killing already completed job
gives ambiguous message as "Killed job "
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated MAPREDUCE-4431:
-------------------------------
Target Version/s: 2.2.0-alpha
Affects Version/s: (was: 3.0.0)
Hadoop Flags: Reviewed
> killing already completed job gives ambiguous message as "Killed job <job id>"
> ------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4431
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4431
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha
> Reporter: Nishan Shetty
> Assignee: Devaraj K
> Priority: Minor
> Attachments: MAPREDUCE-4431-1.patch, MAPREDUCE-4431.patch
>
>
> If we try to kill the already completed job by the following command it gives ambiguous message as "Killed job <job id>"
> ./mapred job -kill <already completed job id>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira