hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18226) Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
Date Mon, 19 Jun 2017 19:02:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054599#comment-16054599

Duo Xu commented on HBASE-18226:


Thanks for reviewing the patch. I can confirm that rDNS never works in our non-secure clusters.
That's why you see our clusters are all using IPs as part of the servername.

Yes, I built the server jar locally and replaced it on an Azure cluster and it was working
fine. All the nodes are using FQDN instead of IP now.

The change we are going to make in non-secure clusters is to add an entry in every node's

VM IP        VM Full FQDN          VM Name 

In this way, we can get the FQDN name of the VM based on its IP. This capability is used for
cleaning up orphan VMs which are not deleted successfully when users delete the cluster, not
related to HBase actually.

However, we saw this change breaking HBase. Because HMaster cannot do reverse DNS lookup and
cannot return FQDN of RS, it returns IP as always.
|| ||RS see itself||HMASTER see RS||
|Before the /etc/hosts change|IP|IP|
|After the /etc/hosts change|FQDN|IP|

With the patch in this JIRA, we can set the configuration to true in our non-secure clusters
so that HMaster side will use RS FQDN too.

Regarding the configuration name, I came up with that name because by default the RegionServerStartupRequest
does not include the RS hostname. Your suggested name is also OK to me. I will change it.

> Disable reverse DNS lookup at HMaster and use default hostname provided by RegionServer
> ---------------------------------------------------------------------------------------
>                 Key: HBASE-18226
>                 URL: https://issues.apache.org/jira/browse/HBASE-18226
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Xu
>         Attachments: HBASE-18226.001.patch, HBASE-18226.002.patch, HBASE-18226.003.patch,
> Description updated:
> In some unusual network environment, forward DNS lookup is supported while reverse DNS
lookup may not work properly.
> This JIRA is to address that HMaster uses the hostname passed from RS instead of doing
reverse DNS lookup to tells RS which hostname to use during reportForDuty() . This has already
been implemented by HBASE-12954 by adding "useThisHostnameInstead" field in RegionServerStatusProtos.
> Currently "useThisHostnameInstead" is optional and RS by default only passes port, server
start code and server current time info to HMaster during RS reportForDuty(). In order to
use this field, users currently need to specify "hbase.regionserver.hostname" on every regionserver
node's hbase-site.xml. This causes some trouble in
> 1. some deployments managed by some management tools like Ambari, which maintains the
same copy of hbase-site.xml across all the nodes.
> 2. HBASE-12954 is targeting multihomed hosts, which users want to manually set the hostname
value for each node. In the other cases (not multihomed), I just want RS to use the hostname
return by the node and set it in useThisHostnameInstead and pass to HMaster during reportForDuty().
> I would like to introduce a setting that if the setting is set to true, "useThisHostnameInstead"
will be set to the hostname RS gets from the node. Then HMaster will skip reverse DNS lookup
because it sees "useThisHostnameInstead" field is set in the request.
> "hbase.regionserver.hostname.reported.to.master", is it a good name?
> --------------------
> Regarding the hostname returned by the RS node, I read the source code again (including
hadoop-common dns.java). By default RS gets hostname by calling InetAddress.getLocalHost().getCanonicalHostName().
If users specify "hbase.regionserver.dns.interface" or "hbase.regionserver.dns.nameserver"
or some underlying system configuration changes (eg. modifying /etc/nsswitch.conf), it may
first read from DNS or other sources instead of first checking /etc/hosts file.

This message was sent by Atlassian JIRA

View raw message