[jira] [Created] (HBASE-5996) Improve multiPut/multiDelete by moving HLog.append and updateTimestamp out of the updateLock.readLock.lock()/unlock() functionality

["Amitanand Aiyer (JIRA)" <ji...@apache.org>]

Amitanand Aiyer created HBASE-5996:
--------------------------------------

             Summary: 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.94.0, 0.89-fb
            Reporter: Amitanand Aiyer
            Assignee: 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 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