hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Created: (HBASE-3656) 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
Date Wed, 16 Mar 2011 17:03:29 GMT
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: stack


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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message