You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2019/05/06 02:20:00 UTC

[jira] [Comment Edited] (HBASE-17028) New 2.0 blockcache (tinylfu) doesn't have inmemory partition, etc Update doc and codebase accordingly

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

Biju Nair edited comment on HBASE-17028 at 5/6/19 2:19 AM:
-----------------------------------------------------------

The attached patch to update the doc helps? [~stack], [~anoop.hbase]


was (Author: gsbiju):
The patch to update the doc helps? [~stack], [~anoop.hbase]

> New 2.0 blockcache (tinylfu) doesn't have inmemory partition, etc Update doc and codebase accordingly
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17028
>                 URL: https://issues.apache.org/jira/browse/HBASE-17028
>             Project: HBase
>          Issue Type: Sub-task
>          Components: BlockCache
>            Reporter: stack
>            Priority: Major
>         Attachments: HBASE-17028.patch
>
>
> Intent is to make the parent tinylfu blockcache default on in 2.0 replacing our old lru blockcache. This issue is about making it clear in doc and code how the new blockcache differs from the old (You can put back the old lru blockcache with config change).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)