[ https://issues.apache.org/jira/browse/HBASE-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212143#comment-13212143 ]
Hudson commented on HBASE-5393: ------------------------------- Integrated in HBase-0.92-security #91 (See [https://builds.apache.org/job/HBase-0.92-security/91/]) HBASE-5393 Consider splitting after flushing (Revision 1245726) Result = FAILURE jdcryans : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreFlusher.java > Consider splitting after flushing > --------------------------------- > > Key: HBASE-5393 > URL: https://issues.apache.org/jira/browse/HBASE-5393 > Project: HBase > Issue Type: Improvement > Affects Versions: 0.90.5 > Reporter: Jean-Daniel Cryans > Assignee: Jean-Daniel Cryans > Fix For: 0.94.0, 0.92.1 > > Attachments: HBASE-2375-flush-split.patch > > > Spawning this from HBASE-2375, I saw that it was much more efficient > compaction-wise to check if we can split right after flushing. Much like the > ideas that Jon spelled out in the description of that jira, the window is > smaller because you don't have to compact and then split right away to only > compact again when the daughters open. > Another thing it improves is while we're normally waiting for the compaction > to happen, data that's still coming in will make us go way past the > MAX_FILESIZE to a point where for the first region I was seeing a store size > 3-4x bigger before it was able to split. > I targeted this for 0.94, but I'd like to get this into 0.92.1 or .2 too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira