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

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_r119487987
  
    --- 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.
    --- End diff --
    
    Might want to add that configuring HA for both is advised?  Also, this 
section uses the abbreviated term "Ranger Admin" throughout, which seems 
confusing to me.  Should probably stick with "Ranger Administration Host" to 
stay consistent with the first part of the doc.


> 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