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

Posted to issues@ambari.apache.org by "bhuvnesh chaudhary (JIRA)" <ji...@apache.org> on 2016/04/13 02:56:25 UTC

[jira] [Assigned] (AMBARI-15849) Activate HAWQ standby wizard fails to delete previous hawq standby master

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

bhuvnesh chaudhary reassigned AMBARI-15849:
-------------------------------------------

    Assignee: bhuvnesh chaudhary

> 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)