[jira] [Commented] (HBASE-17662) Disable in-memory flush when eplaying from WAL

["Anastasia Braginsky (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-17662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873749#comment-15873749 ] 

Anastasia Braginsky commented on HBASE-17662:
---------------------------------------------

Added a patch with a small fix that disables the in-memory-flush while replaying the edits from WAL.

It can be seen in: https://reviews.apache.org/r/56822/

[~stack], [~anoop.hbase], [~ram_krish], [~ebortnik], [~eshcar], please take a look.

Thanks!

> Disable in-memory flush when eplaying 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
>
>
> 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)