[
https://issues.apache.org/jira/browse/HBASE-27183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564500#comment-17564500
]
Duo Zhang edited comment on HBASE-27183 at 7/9/22 3:14 AM:
-----------------------------------------------------------
If the trick is done outside HBase, I think the correct way to address the
remaining problem should also be done outside HBase.
That means, you can implement something like a reverse proxy by your own, and
expose this reverse proxy to all the region server. The related trick logic can
be included in this reverse proxy.
FWIW, I do not feel like this is a general enough scenario which worth to add
new stuff in HBase. For example, if masters are deployed with K8s, sometimes
both the host name and port which are registered to zookeeper can not be
directly connected, then we should also include a special host name field in
the proto? And even on master we can not know what is the valid host name...
Let's discuss more here or on the mailing list, before we land the actual
changes.
Thanks.
was (Author: apache9):
If the trick is done outside HBase, I think the correct way to address the
remaining problem should also be done outside HBase.
That means, you can implement something like a reverse proxy, by our own, and
expose this reverse proxy to all the region server. The related trick logic can
be included in this reverse proxy.
FWIW, I do not feel like this is a general enough scenario which worth to add
new stuff in HBase. For example, if masters are deployed with K8s, sometimes
both the host name and port which are registered to zookeeper can not be
directly connected, then we should also include a special host name field in
the proto? And even on master we can not know what is the valid host name...
Let's discuss more here or on the mailing list, before we land the actual
changes.
Thanks.
> Support regionserver to connect to HMaster proxy port
> -----------------------------------------------------
>
> Key: HBASE-27183
> URL: https://issues.apache.org/jira/browse/HBASE-27183
> Project: HBase
> Issue Type: Improvement
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4
>
>
> Regionservers get active master address from Zookeeper/Master registry and
> tries to make RPC calls to master.
> For security concerns, regionservers might require making connection to a
> different proxy port of master rather than it's original port retrieved from
> Zookeeper.
> Configs:
> # hbase.master.expose.proxy.port: Master can use this config (int) to expose
> new proxy port on active and backup master znodes.
> # hbase.regionserver.consume.master.proxy.port: Clients/Regionservers can
> use this config (boolean) to determine whether to connect to active master on
> new proxy port that master has exposed or continue using original port of
> master for connection.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
