[
https://issues.apache.org/jira/browse/HBASE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215220#comment-13215220
]
stack commented on HBASE-5349:
------------------------------
Chatting w/ J-D about a phenomenon where we do not use memory when we are
taking on a bunch of writes w/ a low region count.
The few regions we have grow to their max of 128M or so and then we flush but
in his case he had gigs of free memory still. The notion is that we should let
memstores grow to fill all available space and then flush when they hit the
low-water global mem mark for the memstore.
The problem then becomes we'll flush lots of massive files and will overwhelm
compactions. We'll need a push-back, something like a flush-merge where we
flush by rewriting an existing store file interleaving the contents of memory
or some such to slow down the flush but also to make for less compaction to do.
> 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
> Fix For: 0.94.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
