[
https://issues.apache.org/jira/browse/HBASE-12943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HBASE-12943:
--------------------------------
Attachment: 12943-1-master.txt
We did some testing on Azure recently. We needed to do two things:
1. Set networkaddress.cache.ttl in the file
${JAVA_HOME}/jre/lib/security/java.security to a certain number for the cache
expiry.
2. Fix code to not use an invalid stubKey (patch attached). Without the patch,
the master wouldn't be able to talk to the just-started RegionServer (same
hostname but a different IP).
> 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
> Attachments: 12943-1-master.txt
>
>
> 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)
