You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/14 22:18:00 UTC

[jira] [Resolved] (HBASE-7050) Document locking of HRegion

     [ https://issues.apache.org/jira/browse/HBASE-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-7050.
----------------------------------------
    Resolution: Not A Problem

> Document locking of HRegion
> ---------------------------
>
>                 Key: HBASE-7050
>                 URL: https://issues.apache.org/jira/browse/HBASE-7050
>             Project: HBase
>          Issue Type: Task
>          Components: documentation, Transactions/MVCC
>            Reporter: Gregory Chanan
>            Priority: Minor
>
> Would be good to have some documentation on the locking in HRegion.  In particular, the updateLock and the row locks.
> With the optimizations that have been made, e.g. HBASE-5541 this isn't straightforward.
> When do these locks need to be held?  What structures do they protect access to?  Why does the updateLock not need to be held during rollback?  Those sorts of questions.
> I've started do to some of this, but haven't fully fleshed it out.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)