ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-13827) hawq standby stop is not working
Date Wed, 11 Nov 2015 23:45:10 GMT


Hadoop QA commented on AMBARI-13827:

{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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:


Test results:
Console output:

This message is automatically generated.

> hawq standby stop is not working
> --------------------------------
>                 Key: AMBARI-13827
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: trunk
>            Reporter: bhuvnesh chaudhary
>            Assignee: bhuvnesh chaudhary
>            Priority: Minor
>             Fix For: trunk
>         Attachments: AMBARI-13827.patch
> For hawq we check if postgres process is existing before stopping hawq daemons (master,
standby, segments). 
> However for active hawq master and segment postgres process should be checked but for
standby gpsyncmaster process should be checked.

This message was sent by Atlassian JIRA

View raw message