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

Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2018/04/20 02:53:00 UTC

[jira] [Commented] (HBASE-15950) Fix memstore size estimates to be more tighter

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

Lars Hofhansl commented on HBASE-15950:
---------------------------------------

Gentlemen, please see HBASE-20459.

 

> Fix memstore size estimates to be more tighter
> ----------------------------------------------
>
>                 Key: HBASE-15950
>                 URL: https://issues.apache.org/jira/browse/HBASE-15950
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>            Priority: Major
>             Fix For: 1.4.0, 2.0.0
>
>         Attachments: Screen Shot 2016-06-02 at 8.48.27 PM.png, hbase-15950-v0.patch, hbase-15950-v1.patch, hbase-15950-v2.branch-1.patch, hbase-15950-v2.branch-1.patch, hbase-15950-v2.patch
>
>
> While testing something else, I was loading a region with a lot of data. Writing 30M cells in 1M rows, with 1 byte values. 
> The memstore size turned out to be estimated as 4.5GB, while with the JFR profiling I can see that we are using 2.8GB for all the objects in the memstore (KV + KV byte[] + CSLM.Node + CSLM.Index). 
> This obviously means that there is room in the write cache that we are not effectively using. 



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