[
https://issues.apache.org/jira/browse/HBASE-27304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581958#comment-17581958
]
LiangJun He commented on HBASE-27304:
-------------------------------------
[~zhangduo] sir, thank you for your comments.
Because the RegionServer address of the meta table obtained by the client from
ZK and the RegionServer address of the region obtained from the meta are all
hostnames by default, but if the client can not resolve the hostname of these
machine, the client cannot access the HBase cluster through hostname.
In our scenario, for elastically scalable HBase nodes on the cloud, the new
node's hostname may not be resolved on the client.
However, if the client and the HBase cluster network are interconnected, the
client can access the HBase cluster through ip, and these ips of the
RegionServer is obtained from the ZK or meta table, so the HBase cluster needs
to use IP to expose Master/RS servers.
We can use hostname by default, but at the same time, we can also provide a
configuration to decide whether to use ip.
> Support using IP to expose master/rs servers for some special scenarios
> -----------------------------------------------------------------------
>
> Key: HBASE-27304
> URL: https://issues.apache.org/jira/browse/HBASE-27304
> Project: HBase
> Issue Type: New Feature
> Components: master, regionserver
> Affects Versions: 3.0.0-alpha-4
> Reporter: LiangJun He
> Assignee: LiangJun He
> Priority: Minor
> Fix For: 3.0.0-alpha-4
>
>
> In our cloud environment, when accessing the HBase cluster from another
> cluster (such as the Flink cluster), you cannot use the hostname to access
> the HBase cluster, but you can use IP. Because it is possible that the
> hostname of the HBase cluster automatic expansion node is not maintained in
> the Flink cluster. So we should support using IP to expose master/rs servers
> for this special scenarios.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
