[
https://issues.apache.org/jira/browse/HBASE-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762377#comment-15762377
]
Devaraj Das commented on HBASE-17294:
-------------------------------------
[~eshcar] from your release note, it seems BASIC is beneficial for all cases.
Can you please elaborate? Do you have benchmarks around this to prove? And also
for the EAGER policy, are there benchmarks? Pardon me if I have missed it but
it doesn't show up here
https://docs.google.com/document/d/10k4hqi4mCCpVrPodp1Q4rV0XsZ4TZtULOa-FOoe-_hw/edit
This is a lot of code (and thanks for the deep work), and I'd definitely want
to see benchmarks / results / benefits before we can ship this in a release.
> External Configuration for Memory Compaction
> ---------------------------------------------
>
> Key: HBASE-17294
> URL: https://issues.apache.org/jira/browse/HBASE-17294
> Project: HBase
> Issue Type: Sub-task
> Reporter: Eshcar Hillel
> Assignee: Eshcar Hillel
> Fix For: 2.0.0
>
> Attachments: HBASE-17294-V01.patch, HBASE-17294-V02.patch,
> HBASE-17294-V03.patch
>
>
> We would like to have a single external knob to control memstore compaction.
> Possible memstore compaction policies are none, basic, and eager.
> This sub-task allows to set this property at the column family level at table
> creation time:
> {code}
> create ‘<tablename>’,
> {NAME => ‘<cfname>’,
> IN_MEMORY_COMPACTION => ‘<NONE|BASIC|EAGER>’}
> {code}
> or to set this at the global configuration level by setting the property in
> hbase-site.xml, with BASIC being the default value:
> {code}
> <property>
> <name>hbase.hregion.compacting.memstore.type</name>
> <value><NONE|BASIC|EAGER></value>
> </property>
> {code}
> The values used in this property can change as memstore compaction policies
> evolve over time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
