[
https://issues.apache.org/jira/browse/AMBARI-14820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15129505#comment-15129505
]
Hadoop QA commented on AMBARI-14820:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12785893/AMBARI-14820-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5167//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5167//console
This message is automatically generated.
> Implement Activate HAWQ Standby wizard to allow doing failover in HA mode
> -------------------------------------------------------------------------
>
> Key: AMBARI-14820
> URL: https://issues.apache.org/jira/browse/AMBARI-14820
> Project: Ambari
> Issue Type: New Feature
> Components: stacks
> Affects Versions: trunk
> Reporter: bhuvnesh chaudhary
> Assignee: bhuvnesh chaudhary
> Fix For: trunk
>
> Attachments: AMBARI-14820-1.patch, AMBARI-14820.patch
>
>
> h1. Activate HAWQ Standby Wizard
> h4. Abstract:
> All configuration changes done on Ambari managed clusters must be done via
> Ambari, otherwise during restart of services, Ambari pushes the configuration
> stored in its database and overwrites the changes done manually.
> Activation of HAWQ Standby to active master involves manual command execution
> which updates the configuration files. In order to keep the configuration in
> sync and reflect the correct state of the HAWQ components on Ambari, we need
> to introduce a wizard, i.e *“Activate HAWQ Standby Wizard”*.
> This wizard will also automate the process of activating standby and the user
> now will need to walk-through the wizard to activate standby.
> h4. Overview of activate standby operation:
> * In HA configuration, HAWQ is configured with a master and standby
> component.
> * To activate / promote standby to a master, “hawq activate standby” command
> needs to be executed on the standby
> * This operation updates the value of hawq_master_address_host and
> hawq_standby_address_host properties available in hawq-site.xml to below
> ** hawq_master_address_host : Initially Configured HAWQ Standby Host
> ** hawq_standby_address_host : This property is removed.
> * After the operation is completed, HAWQ cluster will be running in non-ha
> mode and will not have a configured standby.
> h4. Overview of the wizard pages and operation performed:
> The wizard consists of 3 pages, a brief of them is as below:
> # “Get Started”: This page is the first page seen by the user, and it gives
> introduction of the activity going to be performed.
> # “Review”: This page is the second page which informs the user about the
> changes which will happen. A confirmation is requested before proceeding to
> the next step.
> # “Configure Components”: This page is the third and last page which shows
> the progress for the steps executed. It does the below:
> ## Execute command to activate HAWQ standby
> ## Stop HAWQ service
> ## Reconfigure HAWQ to push updated configs
> ### hawq_standby_address_host is removed
> ### hawq_master_address_host is updated to previous standby
> ## Install HAWQ Master Ambari Component on the Standby Host
> ## Delete HAWQ Standby Ambari Component on the Standby Host
> ## Delete HAWQ Master Ambari Component on the Master host
> ## Start HAWQ Service
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
