[
https://issues.apache.org/jira/browse/HBASE-14920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268734#comment-15268734
]
Anoop Sam John commented on HBASE-14920:
----------------------------------------
IMHO, when a user calls to flush a region, all the cells must get flushed to
disk. It is an explicit call for that from user.
Also yes agree to the fact that the flush tried to reduce the heap usage of the
memstore and flushing only part do this. But the selection of the region for
flushing is done with assumption that the flush call will release all memstore
heap size. (What is there at that time) It can happen that when flush is
called the pipeline have entries and active also almost near to in memory flush
size. The heap size occupied by active is considerably high (specially with
small sized cells) because of the overhead part.
> Compacting Memstore
> -------------------
>
> Key: HBASE-14920
> URL: https://issues.apache.org/jira/browse/HBASE-14920
> Project: HBase
> Issue Type: Sub-task
> Reporter: Eshcar Hillel
> Assignee: Eshcar Hillel
> Attachments: HBASE-14920-V01.patch, HBASE-14920-V02.patch,
> HBASE-14920-V03.patch, HBASE-14920-V04.patch, HBASE-14920-V05.patch,
> HBASE-14920-V06.patch, move.to.junit4.patch
>
>
> Implementation of a new compacting memstore with non-optimized immutable
> segment representation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
