[
https://issues.apache.org/jira/browse/MAPREDUCE-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432139#comment-13432139
]
Mayank Bansal commented on MAPREDUCE-4367:
------------------------------------------
The issue as reported without HISTORY server up if configured , user can not
kill the job.
History server does not do anyways in case of kill so in my patch I am short
circuiting the History server in case of kill.
Adding the test case for testing this scenario in case of History server is up
and down.
Thanks,
Mayank
> mapred job -kill tries to connect to history server
> ---------------------------------------------------
>
> Key: MAPREDUCE-4367
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4367
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client, mrv2
> Affects Versions: 0.23.3
> Reporter: Jason Lowe
> Assignee: Mayank Bansal
> Priority: Minor
> Attachments: MAPREDUCE-4367-trunk-v1.patch
>
>
> The {{mapred job -kill}} command attempts to connect to the history server,
> even though it is unrelated to the process of killing a job.
--
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
