You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/17 15:32:00 UTC

[jira] [Resolved] (HBASE-10139) Regionserver should listen on all network interfaces

     [ https://issues.apache.org/jira/browse/HBASE-10139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-10139.
-----------------------------------------
    Resolution: Incomplete

> Regionserver should listen on all network interfaces
> ----------------------------------------------------
>
>                 Key: HBASE-10139
>                 URL: https://issues.apache.org/jira/browse/HBASE-10139
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.96.0
>            Reporter: Rural Hunter
>            Priority: Critical
>
> My hbase cluster is running in LAN network. All master and slaves hostnames are resolved to LAN ip
> like this:
> master 192.168.1.2
> slave1 192.168.1.3
> slave2 192.168.1.4
> ...
> I found some hbase ports are listening on LAN port only for example the region server:
> tcp6 0 0 192.168.1.3:60020 :::* LISTEN
> while zookeeper is listening on all network interfaces:
> tcp6 0 0 :::2181 :::* LISTEN 
> So in this case, although all the servers have WAN ips, It is still impossible
> for the client in WAN to access hbase cluster even I can configure the client to resolve all host names to WAN ip. I think region server should listen on all network interfaces like the zookeeper does.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)