[HBASE-1279] Fix the way hostnames and IPs are handled

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.19.1
• Fix Version/s: 0.19.2, 0.20.0
• Release Note: To tell HBase how to use your DNS configuration, set hbase.regionserver.dns.interface and hbase.regionserver.dns.nameserver in hbase-site.xml just like in hadoop-site.xml
• Assignee: Jean-Daniel Cryans
• Reporter: Jean-Daniel Cryans
• Created: 20/Mar/09 14:48
• Updated: 13/Sep/09 22:24
• Resolved: 04/May/09 18:35

Description

From the list by Yabo-Arber Xu,

Yes, I've unlocked the port, and i am actually able to access from the web
UI with a client not running on EC2 to HBase at example.com:60010. It shows
all User Tables, but the Region Servers Address is the EC2 internal address:
domU-12-31-39-00-65-E5.compute-1.internal:60020.

I guess the client fails because it can not connect region server, which
serves only for an internal IP. However, in hbase-site.xml, I did configure
with region server explicitly in its external IP.

<property>
<name>hbase.regionserver</name>
<value>ec2-67-202-57-127.compute-1.amazonaws.com:60020</value>
<description>The host and port a HBase region server runs at.
</description>
</property>

In fact we completely bypass the hostname set in hbase.regionserver, also the hostnames in the web UI are not the good ones. We should do that part like hadoop does.