[
https://issues.apache.org/jira/browse/PIG-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohini Palaniswamy updated PIG-5327:
------------------------------------
Description:
The killJob is invokedby
- grunt kill command
- thread interrupt in Main (mostly in case of Oozie)
- HangingJobKiller during shutdown
killJob tries to kill the DAG again even if it was completed. It closes the
session but does not remove it from the TezSessionManager session pool. Though
both of these are minor issues and have no adverse impact (trying to kill a
done DAG would be ignored by Tez AM and TezSessionManager would later check
status of the session and remove it from the pool) the fix would avoid the two
unnecessary calls to AM.
> Check for DAG status before trying to kill
> ------------------------------------------
>
> Key: PIG-5327
> URL: https://issues.apache.org/jira/browse/PIG-5327
> Project: Pig
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.18.0
>
> Attachments: PIG-5327-1.patch
>
>
> The killJob is invokedby
> - grunt kill command
> - thread interrupt in Main (mostly in case of Oozie)
> - HangingJobKiller during shutdown
> killJob tries to kill the DAG again even if it was completed. It closes the
> session but does not remove it from the TezSessionManager session pool.
> Though both of these are minor issues and have no adverse impact (trying to
> kill a done DAG would be ignored by Tez AM and TezSessionManager would later
> check status of the session and remove it from the pool) the fix would avoid
> the two unnecessary calls to AM.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)