hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5349) Automagically tweak global memstore and block cache sizes based on workload
Date Fri, 13 Dec 2013 00:08:09 GMT

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

Andrew Purtell commented on HBASE-5349:

bq. seems if we tweak block cache dynamically, it's more prone to trigger a gc that moment,

This is largely out of our control, until and unless the JVM exposes some knobs for GC and
early warning signals. Between memstore and blockcache we can't just look at occupancy. 

We can provide a null tuner to remove this as a factor when getting to the bottom of excessive
GCs though.

> Automagically tweak global memstore and block cache sizes based on workload
> ---------------------------------------------------------------------------
>                 Key: HBASE-5349
>                 URL: https://issues.apache.org/jira/browse/HBASE-5349
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.92.0
>            Reporter: Jean-Daniel Cryans
>            Assignee: Anoop Sam John
>             Fix For: 0.99.0
>         Attachments: HBASE-5349_V2.patch, HBASE-5349_V3.patch, HBASE-5349_V4.patch, HBASE-5349_V5.patch,
> Hypertable does a neat thing where it changes the size given to the CellCache (our MemStores)
and Block Cache based on the workload. If you need an image, scroll down at the bottom of
this link: http://www.hypertable.com/documentation/architecture/
> That'd be one less thing to configure.

This message was sent by Atlassian JIRA

View raw message