hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dyozie <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #120: HAWQ-1473 - document ranger plugin se...
Date Wed, 31 May 2017 22:42:25 GMT
Github user dyozie commented on a diff in the pull request:

    --- 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 |
    +## <a name="hawq_rps_check_local_interval"></a>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

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message