[
https://issues.apache.org/jira/browse/HBASE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846393#comment-13846393
]
stack commented on HBASE-5349:
------------------------------
bq. seems if we tweak block cache dynamically, it's more prone to trigger a gc
that moment, right?
Makes sense. We will be disturbing whatever equilibrium that may have been in
place. But if the workload has changed such that it has us changing configs.,
would that alone bring on a GC? I suppose we should have a high friction on
the tweaks.
> 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, WIP_HBASE-5349.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
(v6.1.4#6159)
