hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12751) Allow RowLock to be reader writer
Date Tue, 14 Apr 2015 16:15:13 GMT

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

Elliott Clark updated HBASE-12751:
----------------------------------
    Attachment: HBASE-12751-v5.patch

Letting HadoopQA chew on this one.

This is the final merge of mvcc and sequenceid. Previously they were disjoint sets 1billion
apart. However now it's a late binding mvcc and sequence id.

The patch is a bit rough and the work done is a bit ugly. Pushing mvcc into WalKey is ugly
as sin. However it's the best way I could think of to transit the mvcc down into fshlog.

> Allow RowLock to be reader writer
> ---------------------------------
>
>                 Key: HBASE-12751
>                 URL: https://issues.apache.org/jira/browse/HBASE-12751
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>         Attachments: HBASE-12751-v1.patch, HBASE-12751-v2.patch, HBASE-12751-v3.patch,
HBASE-12751-v4.patch, HBASE-12751-v5.patch, HBASE-12751.patch
>
>
> Right now every write operation grabs a row lock. This is to prevent values from changing
during a read modify write operation (increment or check and put). However it limits parallelism
in several different scenarios.
> If there are several puts to the same row but different columns or stores then this is
very limiting.
> If there are puts to the same column then mvcc number should ensure a consistent ordering.
So locking is not needed.
> However locking for check and put or increment is still needed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message