[
https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14901960#comment-14901960
]
stack commented on HBASE-12751:
-------------------------------
No hanging tests.
All tests passed:
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 36 licence.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache HBase ...................................... SUCCESS [2.014s]
[INFO] Apache HBase - Checkstyle ......................... SUCCESS [0.050s]
[INFO] Apache HBase - Resource Bundle .................... SUCCESS [0.052s]
[INFO] Apache HBase - Annotations ........................ SUCCESS [0.091s]
[INFO] Apache HBase - Protocol ........................... SUCCESS [0.102s]
[INFO] Apache HBase - Common ............................. SUCCESS [0.228s]
[INFO] Apache HBase - Procedure .......................... SUCCESS [0.064s]
[INFO] Apache HBase - Client ............................. SUCCESS [0.285s]
[INFO] Apache HBase - Hadoop Compatibility ............... SUCCESS [0.108s]
[INFO] Apache HBase - Hadoop Two Compatibility ........... SUCCESS [0.098s]
[INFO] Apache HBase - Prefix Tree ........................ SUCCESS [0.099s]
[INFO] Apache HBase - Server ............................. SUCCESS [1.057s]
[INFO] Apache HBase - Testing Util ....................... SUCCESS [0.036s]
[INFO] Apache HBase - Thrift ............................. SUCCESS [0.096s]
[INFO] Apache HBase - Shell .............................. SUCCESS [0.193s]
[INFO] Apache HBase - Integration Tests .................. SUCCESS [0.102s]
[INFO] Apache HBase - Examples ........................... SUCCESS [0.100s]
[INFO] Apache HBase - Rest ............................... SUCCESS [0.107s]
[INFO] Apache HBase - External Block Cache ............... SUCCESS [0.037s]
[INFO] Apache HBase - Assembly ........................... SUCCESS [0.064s]
[INFO] Apache HBase - Shaded ............................. SUCCESS [0.036s]
[INFO] Apache HBase - Shaded - Client .................... SUCCESS [0.032s]
[INFO] Apache HBase - Shaded - Server .................... SUCCESS [0.069s]
[INFO] Apache HBase - Spark .............................. SUCCESS [0.082s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.680s
[INFO] Finished at: Tue Sep 22 05:10:06 UTC 2015
[INFO] Final Memory: 39M/1290M
[INFO] ------------------------------------------------------------------------
Looks like its the javadoc issue and no tests included?
[~eclark] commit?
> 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,
> 12751.rebased.v33.txt, 12751.rebased.v34.txt, 12751.rebased.v35.txt,
> 12751.rebased.v35.txt, 12751.rebased.v35.txt, 12751.v37.txt, 12751.v38.txt,
> 12751.v39.txt, 12751v22.txt, 12751v23.txt, 12751v23.txt, 12751v23.txt,
> 12751v23.txt, 12751v36.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)
