[jira] Resolved: (HBASE-1460) Concurrent LRU Block Cache

["stack (JIRA)" <ji...@apache.org>]

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

stack resolved HBASE-1460.
--------------------------

      Resolution: Fixed
    Release Note: hfile.block.cache.size is not a percentage of total heap rather than absolute number
    Hadoop Flags: [Incompatible change, Reviewed]

Thanks for the patch Jon.

> Concurrent LRU Block Cache
> --------------------------
>
>                 Key: HBASE-1460
>                 URL: https://issues.apache.org/jira/browse/HBASE-1460
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: io
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>             Fix For: 0.20.0
>
>         Attachments: HBASE-1460-v1.patch, HBASE-1460-v2.patch, HBASE-1460-v3.patch, HBASE-1460-v4.patch, HBASE-1460-v5.patch
>
>
> The LRU-based block cache that will be committed in HBASE-1192 is thread-safe but contains a big lock on the hash map.  Under high load, the block cache will be hit very heavily from a number of threads, so it needs to be built to handle massive concurrency.
> This issue aims to implement a new block cache with LRU eviction, but backed by a ConcurrentHashMap and a separate eviction thread.  Influence will be drawn from Solr's ConcurrentLRUCache, however there are major differences because solr treats all cached elements as equal size whereas we are dependent on our HeapSize interface with realistic (though approximate) heap usage.

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