[
https://issues.apache.org/jira/browse/AMBARI-15849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239156#comment-15239156
]
Hadoop QA commented on AMBARI-15849:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12798418/AMBARI-15849.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6405//console
This message is automatically generated.
> Activate HAWQ standby wizard fails to delete previous hawq standby master
> -------------------------------------------------------------------------
>
> Key: AMBARI-15849
> URL: https://issues.apache.org/jira/browse/AMBARI-15849
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: bhuvnesh chaudhary
> Assignee: bhuvnesh chaudhary
> Fix For: 2.2.2
>
> Attachments: AMBARI-15849-branch-2.2.patch, AMBARI-15849.patch
>
>
> Activate HAWQ standby wizard fails to delete previous hawq standby master.
> Currently, HAWQ standby status check is done based on the pid available in a
> directory. This directory is same for HAWQ master and HAWQ standby, thus if
> standby has been activated to active master, status of HAWQ Standby component
> still relies on the file and states it as running, and when an attempt is
> made to remove the standby component, it fails.
> Fixed the hawq component status derivation logic in this patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
