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

ASF GitHub Bot commented on HAWQ-1473:
--------------------------------------

Github user dyozie commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/120#discussion_r119490263
  
    --- Diff: markdown/ranger/ranger-integration-config.html.md.erb ---
    @@ -129,6 +129,64 @@ Once the connection between HAWQ and Ranger is 
configured, you may choose to set
     5. Click **Save** to save your changes.
     6. Select **Service Actions > Restart All** and confirm that you want to 
restart the HAWQ cluster.
     
    +## <a id="enableha"></a>Step 3: (Optional) Register a Standby Ranger 
Plug-in Service
    +
    +The HAWQ Ranger Plug-in Service runs on the HAWQ master node. If this 
service goes down, all HAWQ database operations will fail. Configure a highly 
available HAWQ Ranger Plug-in Service to eliminate possible downtime should 
this situation occur.
    +
    +Ranger Admin high availability and HAWQ Ranger Plug-in Service high 
availability are independent; you can configure HAWQ Ranger Plug-in Service HA 
without configuring HA for Ranger Admin.
    +
    +### Prerequisites <a id="rps_ha_cfg_prereq"></a>
    +
    +Before you configure HAWQ Ranger authentication in high availability mode, 
ensure that you have:
    +
    +- Installed or upgraded to a version of HAWQ that includes support for 
HAWQ Ranger Authentication.
    +
    +- (Optional) Configured Ranger Admin for high availability.
    +
    +- Configured a HAWQ standby master node for your HAWQ cluster.
    +
    +    You must configure a standby master for your HAWQ deployment before 
enabling HAWQ Ranger high availability mode. If you have not configured your 
HAWQ standby master, follow the instructions in [Adding a HAWQ Standby 
Master](../admin/ambari-admin.html#amb-add-standby) (if you manage your HAWQ 
cluster with Ambari) or [Configuring Master 
Mirroring](../admin/MasterMirroring.html#standby_master_configure) (for a 
command-line-managed HAWQ cluster).
    +
    +- Registered the HAWQ Ranger Plug-in Service on your HAWQ master node.
    +
    +    The HAWQ Ranger Plug-in Service runs on the HAWQ master node. If you 
have not yet enabled the Ranger Plug-in Service, refer to [Install Ranger 
Connectivity to HAWQ](ranger-integration-config.html#jar) for registration 
instructions. (Optional) If you have configured Ranger Admin HA, make sure to 
identify the Ranger Admin HA proxy when you enable the plug-in.
    +
    +
    +### Configuring the Standby Ranger Plug-in Service <a 
id="rps_ha_cfg_standbyrps"></a>
    +
    +The standby Ranger Plug-in Service runs on the HAWQ standby master node, 
utilizing the same port number as that when the service runs on the master 
node. To enable HAWQ Ranger high availability, you must register the standby 
Ranger Plug-in Service on the standby master node, and then restart the standby.
    +
    +**Note**: If you configured and registered the master HAWQ Ranger Plug-in 
Service before you initialized your HAWQ standby master node, you do not need 
to perform the steps in this section.
    --- End diff --
    
    This note is confusing.  The last bullet under prerequisites specifically 
states that they should have already registered the master plug-in and standby 
master.  If it's true that setting up the master plug-in first and then 
configuring the standby master automatically registers the standby plug-in, 
then this note should probably appear much earlier (before the prerequisites). 


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

Reply via email to