hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Bautin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6387) Cache DNS lookups in HServerAddress
Date Mon, 16 Jul 2012 16:46:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415369#comment-13415369

Mikhail Bautin commented on HBASE-6387:

@Michael: I still see a lot of references to HServerAddress in trunk. Also, there is a comment

  // Hard to deprecate this class. Its in the API as internal class,
  // in particular as an inner class of HRegionLocation.  Besides, sometimes
  // we do want to serialize a InetSocketAddress; this class can be used then.

But this is a very simple fix that we feel is immediately needed in 89-fb, so if you think
it is of no use in trunk, I am happy to leave it as 89-fb-only.
> Cache DNS lookups in HServerAddress
> -----------------------------------
>                 Key: HBASE-6387
>                 URL: https://issues.apache.org/jira/browse/HBASE-6387
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Mikhail Bautin
> We have noticed that we rely on DNS lookups in some critical paths by using HServerAddress,
and Java only seems to be caching DNS data for 30 seconds by default. Also, if DNS is down,
Java's negative cache of DNS will ensure that many successive attempts fail. However, we cannot
just increase networkaddress.cache.ttl to a large value, because e.g. namenode failover may
require resolving the same DNS name differently. Therefore I propose that we add a DNS lookup
cache in HServerAddress.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message