ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-12923) Ambari Server Restart Kills Program Group
Date Fri, 09 Oct 2015 01:13:26 GMT


Hadoop QA commented on AMBARI-12923:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results:
Console output:

This message is automatically generated.

> Ambari Server Restart Kills Program Group 
> ------------------------------------------
>                 Key: AMBARI-12923
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: David M. Lyle
>         Attachments: AMBARI-12923.patch
> 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

View raw message