Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 16 Jun 2017 19:09:00 +0000 (UTC)
From: "Duo Xu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13080492.1497640088000.35912.1497640140147@Atlassian.JIRA>
In-Reply-To: <JIRA.13080492.1497640088000@Atlassian.JIRA>
References: <JIRA.13080492.1497640088000@Atlassian.JIRA> <JIRA.13080492.1497640088174@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-18226) Disable reverse DNS lookup at
 HMaster and use default hostname provided by RegionServer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 16 Jun 2017 19:09:06 -0000

Duo Xu created HBASE-18226:
------------------------------

             Summary: 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
            Priority: Minor


This JIRA is to address the similar problem as HBASE-12954, but there are some little differences,

1. HBASE-12954 provides the configuration "hbase.regionserver.hostname" so users can configure it on every regionserver with preferred hostnames. However, this configuration cannot be set through Ambari because each regionserver has a different value of this setting.

2. In Azure HDInsight clusters, we want to give each RegionServer/workernode a FQDN by modifying /etc/hosts on that node, then when regionserver starts, 
{code}
String hostName = shouldUseThisHostnameInstead() ? useThisHostnameInstead :
      rpcServices.isa.getHostName();
{code}
it uses FQDN names here but on HMaster side, it will do reverse DNS lookup which cannot be resolved.
{code}
 // if regionserver passed hostname to use,
 // then use it instead of doing a reverse DNS lookup
 ServerName rs = master.getServerManager().regionServerStartup(request, ia);
{code}

My proposed fix is to add a new configuration "hbase.hmaster.skip.reverse.dns.lookup". This is a hard switch. If it is set to true, then Regionserver will use the value returned by *_rpcServices.isa.getHostName()_* as the hostname overwriting whatever users specifies in "hbase.regionserver.hostname" and send to HMaster. HMaster will not do reverse DNS lookup, which has been implemented in HBASE-12954. If users want to provide their own hostnames in "hbase.regionserver.hostname", "hbase.hmaster.skip.reverse.dns.lookup" must be false.

I will submit a patch later today.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)