hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Duxbury (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-407) Client should cache region locations in an LRU structure
Date Tue, 12 Feb 2008 18:59:08 GMT

     [ https://issues.apache.org/jira/browse/HBASE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Bryan Duxbury updated HBASE-407:

    Attachment: 407-v4.patch

Removed unneeded imports and comments from HConnectionManager, moved declaration of cachedRegionLocations
all to one place. 

Cleaned bookend debug logging from SoftSortedMap, and improved get and remove so that they
can handle nulls better. 

If the GC nulls a reference between checkReferences and the actual get, it doesn't matter;
the SoftValue will still be in the map, and get() will return null. However, I wasn't taking
into account the situation when the key being checked for actually wasn't in the map, so that
could have let to some NPEs.

> Client should cache region locations in an LRU structure
> --------------------------------------------------------
>                 Key: HBASE-407
>                 URL: https://issues.apache.org/jira/browse/HBASE-407
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>         Attachments: 407-v2.patch, 407-v3.patch, 407-v4.patch, 407.patch
> Instead of keeping the region locations cached client side in a TreeMap, we should use
an LRU mechanism to help manage memory more dynamically.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message