You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2015/04/29 00:32:06 UTC

[jira] [Updated] (OOZIE-2219) Kill child jobs in ActionKillXCommand when sequence file created

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

Rohini Palaniswamy updated OOZIE-2219:
--------------------------------------
    Summary: Kill child jobs in ActionKillXCommand when sequence file created  (was: Kill pig child jobs in ActionKillXCommand when sequence file created)

> Kill child jobs in ActionKillXCommand when sequence file created
> ----------------------------------------------------------------
>
>                 Key: OOZIE-2219
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2219
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Ryota Egashira
>            Assignee: Ryota Egashira
>
> following is the log of a cleanly killed Pig launcher job. It does write the child ids to the sequence file. We can process the sequence file when there is a kill and kill the child jobs also.
> {code}
> Hadoop Job IDs executed by Pig: job_1429645443900_0012
> <<< Invocation of Pig command completed <<<
> <<< Invocation of Main class completed <<<
> Oozie Launcher, uploading action data to HDFS sequence file: hdfs://gsbl90101.blue.ygrid.yahoo.com:8020/user/dfsload/denseb/0000085-150416151027813-denseb-W/pig_sleep--pig/action-data.seq
> {code}
> https://issues.apache.org/jira/browse/OOZIE-1025 is another jira which will address this issue for all scenarios by using application tags. 
> In this jira we will only kill child jobs if they were managed to be written to the action-data.seq file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)