[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033384#comment-16033384 ] ASF GitHub Bot commented on HAWQ-1473: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-hawq-docs/pull/120 > 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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032142#comment-16032142 ] 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_r119489636 --- 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. +## 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 + +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 + +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. --- End diff -- This paragraph should be merged with the intro paragraph directly under **Step 3**. Right now it repeats some of that info. > 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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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. +## 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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032139#comment-16032139 ] 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_r119488319 --- 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. +## 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 + +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. --- End diff -- Wondering if this first bullet is really needed... > 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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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. +## 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 + +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 + +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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032141#comment-16032141 ] 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_r119492058 --- Diff: markdown/reference/guc/parameter_definitions.html.md.erb --- @@ -2147,6 +2149,14 @@ Identifies the port on which the HAWQ Ranger Plug-in Service runs. The `hawq_rps |-|-|-| | valid port number | 8432 | master, reload | +## hawq\_rps\_check\_local\_interval + +When HAWQ Ranger authentication high availability mode is enabled and the Ranger Plug-in Service is active on the standby master node, HAWQ attempts to switch back to the service located on the master node as soon as it becomes available. The HAWQ master periodically attempts to re-establish contact with the service on the local node, using `hawq_rps_check_local_interval` as the polling time interval (in seconds) for this contact. --- End diff -- This wording is a bit unclear as to whether it's talking about just the standby ranger service being used (which is the intent) vs whether the entire master node is down and the standby plug-in is being used. I think it would be better to repeat the wording used in `ranger-ha.html`, which starts "Should the HAWQ master node fail to communicate with the local Ranger Plug-in Service..." > 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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032140#comment-16032140 ] 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_r119489263 --- 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. +## 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 + +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 --- End diff -- This heading title should just be "Procedure". > 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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027143#comment-16027143 ] 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_r118811043 --- Diff: markdown/ranger/ranger-integration-config.html.md.erb --- @@ -129,6 +129,62 @@ 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. +## 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. + +### Prerequisites + +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. + +- 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. Make sure to identify the Ranger Admin HA proxy when you enable the plug-in. --- End diff -- This is not required. > 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)
[jira] [Commented] (HAWQ-1473) document ranger plug-in service high availability
[ https://issues.apache.org/jira/browse/HAWQ-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027144#comment-16027144 ] 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_r118811032 --- Diff: markdown/ranger/ranger-integration-config.html.md.erb --- @@ -129,6 +129,62 @@ 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. +## 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. + +### Prerequisites + +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. + +- Configured Ranger Admin for high availability. --- End diff -- Actually Ranger HA and RPS HA are two separated and independent parts. If the user does not configure Ranger HA, he can also configure RPS HA in HAWQ standby master. > 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)
