[
https://issues.apache.org/jira/browse/HBASE-27304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
LiangJun He updated HBASE-27304:
--------------------------------
Release Note:
In some scenarios, such as the elastic scaling scenario on the cloud, the HBase
client may not be able to resolve the hostname of the newly added node. If the
network is interconnected, the client can actually access the HBase cluster
nodes through ip. However, since the HBase client obtains the Master/RS address
info from or the ZK or the meta table, so the Master/RS of the HBase cluster
needs to expose the service with ip instead of the hostname. Therefore, We can
use hostname by default, but at the same time, we can also provide a config
‘hbase.server.useip.enabled’
to support whether to use ip for Master/RS service.
> 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: 2.6.0, 3.0.0-alpha-4
>
>
> In our 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)
