Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 19 Mar 2015 00:07:40 +0000 (UTC)
From: "Nate Edel (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12763496.1419354012000.137807.1426723660315@Atlassian.JIRA>
In-Reply-To: <JIRA.12763496.1419354012000@Atlassian.JIRA>
References: <JIRA.12763496.1419354012000@Atlassian.JIRA>
 <JIRA.12763496.1419354012824@arcas>
Subject: [jira] [Updated] (HBASE-12751) Allow RowLock to be reader writer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nate Edel updated HBASE-12751:
------------------------------
    Status: In Progress  (was: Patch Available)

> 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: Nate Edel
>         Attachments: HBASE-12751-v1.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)