[
https://issues.apache.org/jira/browse/HBASE-17081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760460#comment-15760460
]
Eshcar Hillel commented on HBASE-17081:
---------------------------------------
Just some clarification w.r.t. which memstore is running:
First we look at the in_memory_compaction property at the cf level (no default
choice here);
if it is not set we look at the global properties set by hbase-site.xml, with
Basic compaction being the default (as agreed);
if the property is set to None then we set memstore to the class defined by
memstore_class_name, with default memstore being the default.
[~anoop.hbase] why do you say we are not ready for basic compaction being the
default?
This is the intention for 2.0, and all tests seem to pass (at least they did).
If there is still some problem with a specific test that requires being run
with no compaction, this can be easily set with
{code}
conf.set(CompactingMemStore.COMPACTING_MEMSTORE_TYPE_KEY,
String.valueOf(HColumnDescriptor.MemoryCompaction.NONE));
{code}
> Flush the entire CompactingMemStore content to disk
> ---------------------------------------------------
>
> Key: HBASE-17081
> URL: https://issues.apache.org/jira/browse/HBASE-17081
> Project: HBase
> Issue Type: Sub-task
> Reporter: Anastasia Braginsky
> Assignee: Anastasia Braginsky
> Attachments: HBASE-15787_8.patch, HBASE-17081-V01.patch,
> HBASE-17081-V02.patch, HBASE-17081-V03.patch, HBASE-17081-V04.patch,
> HBASE-17081-V05.patch, HBASE-17081-V06.patch, HBASE-17081-V06.patch,
> HBASE-17081-V07.patch, HBaseMeetupDecember2016-V02.pptx,
> Pipelinememstore_fortrunk_3.patch
>
>
> Part of CompactingMemStore's memory is held by an active segment, and another
> part is divided between immutable segments in the compacting pipeline. Upon
> flush-to-disk request we want to flush all of it to disk, in contrast to
> flushing only tail of the compacting pipeline.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
