[
https://issues.apache.org/jira/browse/HBASE-8228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694064#comment-13694064
]
Himanshu Vashishtha commented on HBASE-8228:
--------------------------------------------
bq. Swapping the order of the HRegion.updatesLock.writeLock(), and
startCacheFlush should probably fix this issue.
So, you don't lock the region until you get the cacheFlushLock.readLock().
In 0.94, cacheFlushLock is still a ReentrantLock. I wonder whether multiple
memstore flush threads help there at all (if multiple flushers are there in
0.94).
In trunk, we no longer write flush events to hlog. Basically, a flush can
happen while log rolling is going on.
> Investigate time taken to snapshot memstore
> -------------------------------------------
>
> Key: HBASE-8228
> URL: https://issues.apache.org/jira/browse/HBASE-8228
> Project: HBase
> Issue Type: Sub-task
> Reporter: Amitanand Aiyer
> Assignee: Amitanand Aiyer
> Priority: Minor
> Fix For: 0.89-fb
>
>
> Snapshotting memstores is normally quick. But, sometimes it seems to take
> long. This JIRA is to track the investigation and fix to improve the outliers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
