hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Luis Navarro (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-18443) RegionServer register twice if there is no reverse DNS lookup available
Date Mon, 24 Jul 2017 10:49:00 GMT
Jose Luis Navarro created HBASE-18443:

             Summary: RegionServer register twice if there is no reverse DNS lookup available
                 Key: HBASE-18443
                 URL: https://issues.apache.org/jira/browse/HBASE-18443
             Project: HBase
          Issue Type: Bug
          Components: master, regionserver
    Affects Versions: 1.1.2
         Environment: Centos 7 on Microsoft Azure
HBase 1.1.2 provided by Hortonworks HDP 2.5 stack
Installed and managed with Apache Ambari
            Reporter: Jose Luis Navarro
            Priority: Minor

HBase does not complain if there is no reverse DNS lookup possible for the master or regionserver

If the master is unable to verify the identity of a regionserver using the reverse DNS lookup,
the node is added twice to the list of available regionservers (Once with the FQDN the node
presents itself and another one as the IP address).
When this happens HBase is unusable and metadata is corrupted.

Hadoop also relies on reverse DNS but it complains if it is not possible to honor it unless
you explicitly disable the lookup in the configuration. On the other hand HBase does not complain
and simply does not work if the reverse lookup is not posible.

It can be fixed by simply adding entries to /etc/hosts file with the regionservers, but this
can become unmanageable if the cluster can grow dynamically in a cloud service like Azure.

This message was sent by Atlassian JIRA

View raw message