You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/04/11 03:31:14 UTC
[jira] [Resolved] (HBASE-5996) Improve multiPut/multiDelete by
moving HLog.append and updateTimestamp out of the
updateLock.readLock.lock()/unlock() functionality
[ https://issues.apache.org/jira/browse/HBASE-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-5996.
-----------------------------------
Resolution: Incomplete
Assignee: (was: Amitanand Aiyer)
> Improve multiPut/multiDelete by moving HLog.append and updateTimestamp out of the updateLock.readLock.lock()/unlock() functionality
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5996
> URL: https://issues.apache.org/jira/browse/HBASE-5996
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.89.20100924, 0.89-fb, 0.94.0
> Reporter: Amitanand Aiyer
> Priority: Minor
>
> whenever we do a batchMutateWithLocks in HRegion,
> we get the HRegion.updateLock.readLock() ...
> My understanding is that we need the updateLock.readLock only
> to protect the updates to the memStore.
> (i) HLog.append() has its own serialization/locking using HLog.updateLock
> We can move this out of the HRegion.updateLock lock grabbing.
> (ii) updating the timestamp for deltes and puts, can also be done before
> grabbing the lock.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)