[ https://issues.apache.org/jira/browse/HBASE-17662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877747#comment-15877747 ]
Anastasia Braginsky commented on HBASE-17662: --------------------------------------------- [~anoop.hbase], [~ram_krish], I have addressed all the issues you raised in the code review. Please take a look on the recent version in the review board. Please consider for commit as the last patch passes the QA. Thanks! > Disable in-memory flush when replaying from WAL > ----------------------------------------------- > > Key: HBASE-17662 > URL: https://issues.apache.org/jira/browse/HBASE-17662 > Project: HBase > Issue Type: Sub-task > Reporter: Anastasia Braginsky > Attachments: HBASE-17662-V02.patch, HBASE-17662-V03.patch > > > When replaying the edits from WAL, the region's updateLock is not taken, > because a single threaded action is assumed. However, the thread-safeness of > the in-memory flush of CompactingMemStore is based on taking the region's > updateLock. > The in-memory flush can be skipped in the replay time (anyway everything is > flushed to disk just after the replay). Therefore it is acceptable to just > skip the in-memory flush action while the updates come as part of replay from > WAL. -- This message was sent by Atlassian JIRA (v6.3.15#6346)