[
https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027146#comment-16027146
]
ASF GitHub Bot commented on HAWQ-1473:
--------------------------------------
Github user ictmalili commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/120#discussion_r118810915
--- Diff: markdown/admin/MasterMirroring.html.md.erb ---
@@ -103,6 +103,8 @@ Upon activation of the standby master, HAWQ
reconstructs the state of the master
```
The newly-activated master's status should be **Active**. If you
configured a new standby master, its status is **Passive**. When a standby
master is not configured, the command displays `-No entries found`, the message
indicating that no standby master instance is configured.
+
+6. If you have enabled HAWQ Ranger Authentication in high availability
mode in your cluster, you must manually update the Ranger HAWQ service
definition to identify the new master node. Refer to [Failover to HAWQ Standby
Master](../ranger/ranger-ha.html#rps_ha_cfg_masterfailover) in the HAWQ Ranger
documentation for additional information.
6. Query the `gp_segment_configuration` table to verify that segments have
registered themselves to the new master:
--- End diff --
The index number for next item should be incremented.
> document ranger plug-in service high availability
> -------------------------------------------------
>
> Key: HAWQ-1473
> URL: https://issues.apache.org/jira/browse/HAWQ-1473
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Documentation
> Reporter: Lisa Owen
> Assignee: David Yozie
>
> add RPS high availability information to the docs. include config info as
> well as failover scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
