[
https://issues.apache.org/jira/browse/HBASE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705242#action_12705242
]
Shalin Shekhar Mangar commented on HBASE-1192:
----------------------------------------------
Thanks Jonathan.
bq. On the inside, it is very similar to a LinkedHashMap, just customized to be
memory-aware making use of our HeapSize interface. It turned out to be much
easier and more efficient to work with the data structures directly.
Sure, if you find it easier that way, that's fine.
{quote}It is possible we will run in to contention issues. If we saw issues, my
plan was to add buckets a la ConcurrentHashMap.
Looking at the solr implementation, that looks like what you guys did! Very
cool.{quote}
This is what Solr has in trunk right now:
http://svn.apache.org/viewvc/lucene/solr/trunk/src/common/org/apache/solr/common/util/ConcurrentLRUCache.java?view=markup
Also see SOLR-1082 where an ehcache based implementation was also discussed.
> LRU-style map for the block cache
> ---------------------------------
>
> Key: HBASE-1192
> URL: https://issues.apache.org/jira/browse/HBASE-1192
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: regionserver
> Reporter: Jonathan Gray
> Assignee: ryan rawson
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: hbase-1192-v1.patch, hbase-1192-v2.patch,
> hbase-1192-v3.patch
>
>
> We need to decide what structure to use to back the block cache. The primary
> decision is whether to continue using SoftReferences or to build our own
> structure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
