hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1186) Memory-aware Maps with LRU eviction for Cell Cache
Date Sat, 21 Mar 2009 17:25:50 GMT

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

Andrew Purtell commented on HBASE-1186:

I've reviewed this and except for a minor collision with the patch now it looks good. I'm
just waiting for HBASE-1274 to be resolved first so I can claim that all local tests pass
before committing this.

> Memory-aware Maps with LRU eviction for Cell Cache
> --------------------------------------------------
>                 Key: HBASE-1186
>                 URL: https://issues.apache.org/jira/browse/HBASE-1186
>             Project: Hadoop HBase
>          Issue Type: New Feature
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.20.0
>         Attachments: hbase-1186-v2.patch, hbase-1186-v3.patch, hbase-1186-v4.patch, HeapSize.java,
> Caching is key for 0.20.  We need a set of memory-aware data structures to manage our
> I propose two initial classes:  LruHashMap and LruBlockMap
> *LruHashMap* is currently being used over in HBASE-80 for the Cell cache.  Erik Holstad
has done extensive testing and benchmarking and will post results over in this issue.
> - Memory-aware
> - Fixed size
> - LRU eviction
> *LruBlockMap* can be used for the block caching of the new file format in HBASE-61. 
It should try to use all available memory, but must contend with Memcaches so is resizable
to deal with heap pressure.  Adding high priority blocks (evicted last) gives us in-memory
functionality as described in bigtable paper.
> - Memory-aware
> - Fully resizable
> - LRU eviction (with some additions)
> - High priority blocks
> - _Optional: Scan resistant algorithm_
> Part of this issue is also solving how we will determine the size of cached objects.

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

View raw message