[
https://issues.apache.org/jira/browse/HBASE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297668#comment-14297668
]
Enis Soztutar commented on HBASE-12943:
---------------------------------------
We have also seen this causing problems in a cloud environment (azure). If a RS
gets re-imaged and joins the cluster with the same hostname but with a
different ip, the master can never connect to it again.
We have tried setting the {{networkaddress.cache.ttl}} in security
configuration according to the InetSocketAddress / InetAddress javadoc, but it
did not take affect. Documentation for {{sun.net.inetaddr.ttl}} says that it
can be set from command line. If we can get it working, I'm all for it.
> Set sun.net.inetaddr.ttl in HBase
> ---------------------------------
>
> Key: HBASE-12943
> URL: https://issues.apache.org/jira/browse/HBASE-12943
> Project: HBase
> Issue Type: Bug
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
>
> The default value of config: sun.net.inetaddr.ttl is -1 and the java
> processes will cache the mapping of hostname to ip address forever, See:
> http://docs.oracle.com/javase/7/docs/technotes/guides/net/properties.html
> But things go wrong when a regionserver with same hostname and different ip
> address rejoins the hbase cluster. The HMaster will get wrong ip address of
> the regionserver from this cache and every region assignment to this
> regionserver will be blocked for a time because the HMaster can't communicate
> with the regionserver.
> A tradeoff is to set the sun.net.inetaddr.ttl to 10m or 1h and make the wrong
> cache expired.
> Suggestions are welcomed. Thanks~
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
