[jira] [Updated] (OOZIE-3596) When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.

["Suekyoung Lee (Jira)" <ji...@apache.org>]

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

Suekyoung Lee updated OOZIE-3596:
---------------------------------
    Attachment:     (was: OOZIE-3596-001.patch)

> When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-3596
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3596
>             Project: Oozie
>          Issue Type: Improvement
>          Components: core
>            Reporter: Suekyoung Lee
>            Priority: Major
>         Attachments: OOZIE-3596-001.patch
>
>
> When the SSH action is terminated via the kill API, only the ssh-wrapper.sh file (created for ssh execution in oozie) is terminated, and the child-processes that has occurred is still running.
> For example, if the shell file for running spark-shell (e.g. called "run-spark.sh") runs and exits as an SSH action, only the ssh-wrapper.sh file exits and the child-processes (run-spark.sh and spark-shell) are still running.
> Therefore, when the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)