[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985959#comment-15985959 ] Paul Guo commented on HAWQ-1436: If you use the guc with list, you could design it as either load-balancer or master+slaves. > 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985902#comment-15985902 ] Hongxu Ma commented on HAWQ-1436: - About RPS proxy and GNC, can we make a compromise like this: only one GNC: *hawq_rps_url_list*, and its default value is "" (or other specific value) * If the value is "", just behave as design doc 3.1, this is we provide defaultly. * The value can also be configured as a list (e.g. "http://192.168.1.66:1357/suffix, http://192.168.1.88.1357/suffix;), behave a basic RR load-balance as Paul suggested, user can decide whether use this strategy or not. > 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984421#comment-15984421 ] Paul Guo commented on HAWQ-1436: [~xsheng] Typo in my comment. I removed the "do not" word. > 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984355#comment-15984355 ] Lili Ma commented on HAWQ-1436: --- I suggest we do solution 1) to simply the implementation as the first step. Since RPS will only be called by master and a query usually only raises several RPS request, there won't be a lot of requests to RPS. So I think load balancer may be over-design. For services which support a lot of concurrent requests, a proxy server at the front of multiple web Service is an ideal design, since it will be convenient for both HA and load balance. > 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984321#comment-15984321 ] Xiang Sheng commented on HAWQ-1436: --- [~Paul Guo] some of my understanding. Correct me if there are mistakes. [~hongxu ma] what proxy do you say in the doc ? If it's the proxy in the figure of 3.1, the proxy is the ranger server proxy for Ranger server HA. Ranger designed this for their HA. If it's the proxy in the 3.2, after discussed, we won't use that design. GUC hawq_rps_address_suffix and hawq_rps_address_host will be removed. > 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984225#comment-15984225 ] Paul Guo commented on HAWQ-1436: 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15984207#comment-15984207 ] Hongxu Ma commented on HAWQ-1436: - [~adenissov] I am thinking how to deal with the situation you mentioned. Thank you very much! > 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983898#comment-15983898 ] Lei Chang commented on HAWQ-1436: - Nice doc. Can we treat RPS process similar to a resource manager process? postmaster can restart the process automatically. It might potentially simplify the design a lot. > 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)
[jira] [Commented] (HAWQ-1436) Implement RPS High availability on HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15983362#comment-15983362 ] Alexander Denissov commented on HAWQ-1436: -- One issue with "localhost" value for the rps_host is that when RPS will be SSL-enabled, it will have a certificate, ideally issued for the FQDN of the host and this certificate will be imported into HAWQ SSL trust store (or whatever analogy HAWQ is using to store a list of trusted certificates). When SSL connection is established, SSL will verify that the certificate presented by the server contains the host name where the connection is being established to, so HAWQ code would need to translate "localhost" to its own FQDN or employ a similar logic to pass SSL certification validation. > 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)
