[
https://issues.apache.org/jira/browse/HBASE-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052632#comment-16052632
]
Duo Xu edited comment on HBASE-18226 at 6/17/17 1:59 AM:
---------------------------------------------------------
[~ndimiduk]
Thanks for reviewing. I have not check secure HBase. I will setup and do some
sanity test.
Simply, my change is to use the hostname from RS rather than HMaster tells RS
to use the hostname which HMaster gets from reverse DNS lookup of the IP of the
connection socket. It should be no different from HBASE-12954, HBASE-12954 is
using the hostname user specified in the configuration.
I do not know much about secure HBase though, [~elserj] if you can help review
the patch too, that would be great!
was (Author: onpduo):
[~ndimiduk]
Thanks for reviewing. I have not check secure HBase. I will setup and do some
sanity test.
Simply, my change is to use the hostname from RS rather than HMaster tells RS
to use the hostname which HMaster gets from reverse DNS lookup of the IP of the
connection socket. It should be no different from HBASE-18226, HBASE-18226 is
using the hostname user specified in the configuration.
I do not know much about secure HBase though, [~elserj] if you can help review
the patch too, that would be great!
> 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
>
>
> 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 or other
> configuration management tools because each regionserver has a different
> value of this setting, which means each node needs a different hbase-site.xml.
> 2. In Azure HDInsight clusters, we want to give each RegionServer/workernode
> a FQDN by modifying /etc/hosts on that node. We do not want HMaster to do
> reverse DNS lookup because HMaster VM's /etc/hosts does not have regionserver
> VM's FQDN mappings. In current implementation 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.regionserver.hostname.auto*". 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 as part of
> RegionServerStartupRequest. 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.regionserver.hostname.auto*" must
> be false.
> I will submit a patch later today.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
