ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-12923) Ambari Server Restart Kills Program Group
Date Sun, 11 Oct 2015 18:37:05 GMT

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

Eric Yang updated AMBARI-12923:
-------------------------------
    Affects Version/s: 2.1.2
                       1.7.0
        Fix Version/s: 2.1.3
          Component/s: ambari-server

> Ambari Server Restart Kills Program Group 
> ------------------------------------------
>
>                 Key: AMBARI-12923
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12923
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0, 2.1.2
>            Reporter: David M. Lyle
>            Assignee: David M. Lyle
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-12923.patch, 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)

Mime
View raw message