[
https://issues.apache.org/jira/browse/HBASE-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-3656.
----------------------------------------
Resolution: Incomplete
> Merging flush; merge a flush with one of the existing store files (the
> smallest?) so we skip creating a new store file on each flush
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-3656
> URL: https://issues.apache.org/jira/browse/HBASE-3656
> Project: HBase
> Issue Type: Task
> Reporter: Michael Stack
> Priority: Major
>
> This behavior is described in the BT paper. Years ago I had a go at it but
> at the time it slowed flushing significantly -- and IIRC we had no barriers
> on writes when the memory pressue was high -- so it brought on OOMEs... so
> punted on it. Its time to consider this feature again.
> Would we always do it? Maybe not if its a close? If a close we want stuff
> to run quickly so we should skip the merge. But any other time, we should do
> it?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
