You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "David M. Lyle (JIRA)" <ji...@apache.org> on 2015/08/28 21:23:45 UTC

[jira] [Updated] (AMBARI-12923) Ambari Server Restart Kills Program Group

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

David M. Lyle updated AMBARI-12923:
-----------------------------------
    Attachment: AMBARI-12923.patch

Patch to change stop from killpg to kill.

> Ambari Server Restart Kills Program Group 
> ------------------------------------------
>
>                 Key: AMBARI-12923
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12923
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: David M. Lyle
>         Attachments: AMBARI-12923.patch
>
>
> ambari-server.py realizes it kill command with os.killpg(os.getpgid(pid), signal.SIGKILL). This has a undesirable side effect of killing a container when Ambari is launched via Docker under Serf or Consul. I believe it is no longer required.
> Any objection to changing it to os.kill(pid, signal.SIGKILL)? If not, happy to put up a patch.
> Thanks!



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