[
https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737531#comment-14737531
]
stack commented on HBASE-12751:
-------------------------------
TestTags is simple fix (I broke tag handling).
All rest are likely related, yeah. Thanks for that (smile). We used to block on
SyncFuture and if sync failed, we'd clean them all up -- we had a list. Now we
are waiting on latch in WALKey#getWriteEntry too... to get WriteEntry. Let me
see...
> 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
> Affects Versions: 2.0.0, 1.3.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 2.0.0, 1.3.0
>
> Attachments: 12751.rebased.v25.txt, 12751.rebased.v26.txt,
> 12751.rebased.v26.txt, 12751.rebased.v27.txt, 12751.rebased.v29.txt,
> 12751.rebased.v31.txt, 12751.rebased.v32.txt, 12751.rebased.v32.txt,
> 12751v22.txt, 12751v23.txt, 12751v23.txt, 12751v23.txt, 12751v23.txt,
> HBASE-12751-v1.patch, HBASE-12751-v10.patch, HBASE-12751-v10.patch,
> HBASE-12751-v11.patch, HBASE-12751-v12.patch, HBASE-12751-v13.patch,
> HBASE-12751-v14.patch, HBASE-12751-v15.patch, HBASE-12751-v16.patch,
> HBASE-12751-v17.patch, HBASE-12751-v18.patch, HBASE-12751-v19 (1).patch,
> HBASE-12751-v19.patch, HBASE-12751-v2.patch, HBASE-12751-v20.patch,
> HBASE-12751-v20.patch, HBASE-12751-v21.patch, HBASE-12751-v3.patch,
> HBASE-12751-v4.patch, HBASE-12751-v5.patch, HBASE-12751-v6.patch,
> HBASE-12751-v7.patch, HBASE-12751-v8.patch, HBASE-12751-v9.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)
