pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohini Palaniswamy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PIG-5327) Check for DAG status before trying to kill
Date Tue, 09 Jan 2018 13:27:00 GMT

     [ https://issues.apache.org/jira/browse/PIG-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rohini Palaniswamy updated PIG-5327:
------------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

bq. But can you share some background on why you wanted this change?
  Updated the description.

Committed to trunk. Thanks for the review Koji.

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

Mime
View raw message