hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15513) hbase.hregion.memstore.chunkpool.maxsize is 0.0 by default
Date Fri, 02 Sep 2016 15:46:20 GMT

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

stack commented on HBASE-15513:
-------------------------------

[~ram_krish] and [~anoopsamjohn] These are the offheap write tests you did? Want to add a
pointer here?

bq. I have run my own as well and measured memory allocation rate (not latency) and major
GC frequency.

What kind of test was it [~vrodionov] You don't provide data or detail on the test setup.

Offheap write path needs chunkpool on. Fellas who have run the G1GC in production, want pooling
off because it makes their run profile worse. 

> hbase.hregion.memstore.chunkpool.maxsize is 0.0 by default
> ----------------------------------------------------------
>
>                 Key: HBASE-15513
>                 URL: https://issues.apache.org/jira/browse/HBASE-15513
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15513-v1.patch
>
>
> That results in excessive MemStoreLAB chunk allocations because we can not reuse them.
Not sure, why it has been disabled, by default. May be the code has not been tested well?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message