hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6387) Cache DNS lookups in HServerAddress
Date Fri, 13 Jul 2012 07:40:35 GMT

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

stack commented on HBASE-6387:

HServerAddress is deprecated in trunk, replaced. On deserialization was doing a dns lookup.
 So this is 0.89fb only Mikhail?
> 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