[
https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984225#comment-15984225
]
Paul Guo edited comment on HAWQ-1436 at 4/26/17 8:43 AM:
---------------------------------------------------------
Some suggestions:
1) Since RPS has been a stateless proxy to my knowledge, we really do not need
to add an additional proxy service (i.e. http proxy?). i.e. I think 3.1 is
enough. If we really really need to add some logic of the "proxy", you could
add the code logic in hawq.
2) I assume currently we need RPS on master and standby. think in the long run,
we should decouple RPS nodes with master/standby nodes although running RPS is
allowed on master/standby.
3) Since RPS is stateless, maybe we should use or at least allow a load
balancer policy, instead of making the "standby" RPS idle.
4) I really expect combine all of the RPS related GUCs into one (no,
hawq_rps_address_host, hawq_rps_address_port, hawq_rps_address_suffix), e.g.
hawq_rps_url_list (e.g. value with
"http://192.168.1.66:1357/suffix,http://192.168.1.88.1357/suffix"; or with more
nodes?)
Frankly speaking, when I first see hawq_rps_address_suffix, I was really
confused.
was (Author: paul guo):
Some suggestions:
1) Since RPS has been a stateless proxy to my knowledge, we really do not need
to add an additional proxy service (i.e. http proxy?). i.e. I do not think 3.1
is enough. If we really really need to add some logic of the "proxy", you could
add the code logic in hawq.
2) I assume currently we need RPS on master and standby. think in the long run,
we should decouple RPS nodes with master/standby nodes although running RPS is
allowed on master/standby.
3) Since RPS is stateless, maybe we should use or at least allow a load
balancer policy, instead of making the "standby" RPS idle.
4) I really expect combine all of the RPS related GUCs into one (no,
hawq_rps_address_host, hawq_rps_address_port, hawq_rps_address_suffix), e.g.
hawq_rps_url_list (e.g. value with
"http://192.168.1.66:1357/suffix,http://192.168.1.88.1357/suffix"; or with more
nodes?)
Frankly speaking, when I first see hawq_rps_address_suffix, I was really
confused.
> Implement RPS High availability on HAWQ
> ---------------------------------------
>
> Key: HAWQ-1436
> URL: https://issues.apache.org/jira/browse/HAWQ-1436
> Project: Apache HAWQ
> Issue Type: Sub-task
> Components: Security
> Reporter: Hongxu Ma
> Assignee: Hongxu Ma
> Fix For: backlog
>
> Attachments: RPSHADesign_v0.1.pdf
>
>
> Once Ranger is configured, HAWQ will rely on RPS to connect to Ranger. A
> single point RPS may influence the robustness of HAWQ.
> Thus We need to investigate and design out the way to implement RPS High
> availability.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
