ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15926) HAWQ activate standby wizard fails after port number change but before restart.
Date Mon, 18 Apr 2016 23:16:25 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246755#comment-15246755
] 

Hudson commented on AMBARI-15926:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.2 #647 (See [https://builds.apache.org/job/Ambari-branch-2.2/647/])
AMBARI-15926: HAWQ activate standby wizard fails after port number (jaoki: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=980a4d94686446be1bd04ec67cf74f9ec88762bb])
* ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqstandby.py


> HAWQ activate standby wizard fails after port number change but before restart.
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-15926
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15926
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.2
>            Reporter: jun aoki
>            Assignee: jun aoki
>            Priority: Minor
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15926-branch-2.2.v1.patch, AMBARI-15926-trunk.v1.patch
>
>
> Precondition:
> Install HAWQ with master and standby master (HA)
> Steps:
> 1. Go to HAWQ's config and change master port number and standby port number.
> 2. Do not restart HAWQ service
> 3. Run Activate Standby wizard 
> Expected: 
> Succeeded.
> Actual:
> It fails due to probably "hawq activate standby" command transition the standby master
to master with an old port without Ambari knowing it.
> And the following actions (stop) fails because the port number is different.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message