[
https://issues.apache.org/jira/browse/HBASE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847621#comment-13847621
]
stack commented on HBASE-5349:
------------------------------
I think this feature should be on by default. If it is off no one will enable
it because they'll be afraid of what it might do. It should be on because it
takes away a need to twiddle knobs. Regards what happens to GC'ing profile
when there is a seismic shift in size of blockcache/memstore, the point
[~xieliang007] raises, its a valid concern; can we flag it as concern in doc
("If GC'ing sensitive...." or "If low-latency serving...") and release note it
and then spend some time seeing how bad it is in action? Any way we could have
a shift in config balance out? i.e. block cache allocations some subset of
memstore allocations so no more fragmentation....
> 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)
