[
https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494440#comment-14494440
]
Hadoop QA commented on HBASE-12751:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12725267/HBASE-12751-v5.patch
against master branch at commit 4f151444b58ae85b93f76254961358932e0ffb9b.
ATTACHMENT ID: 12725267
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 94 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1928 checkstyle errors (more than the master's current 1910 errors).
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ this.htableDescriptor.getTableName(),
WALKey.NO_SEQUENCE_ID, nonceGroup, nonce, mvcc);
+ final WALEdit edits, final AtomicLong sequenceId, final boolean
inMemstore) throws IOException {
+ long logSeqNum, final long now, List<UUID> clusterIds, long nonceGroup,
long nonce, MultiVersionConsistencyControl mvcc) {
+ final long now, List<UUID> clusterIds, long nonceGroup, long nonce,
final MultiVersionConsistencyControl mvcc) {
+ final long now, List<UUID> clusterIds, long nonceGroup, long nonce,
MultiVersionConsistencyControl mvcc) {
+ long logSeqNum, final long now, List<UUID> clusterIds, long nonceGroup,
long nonce, MultiVersionConsistencyControl mvcc) {
+ long logSeqNum, final long now, List<UUID> clusterIds, long nonceGroup,
long nonce, MultiVersionConsistencyControl mvcc) {
+ long logSeqNum, final long now, List<UUID> clusterIds, long nonceGroup,
long nonce, MultiVersionConsistencyControl mvcc) {
+ long txid = log.append(htd, info, getWalKey(System.currentTimeMillis()),
edit, sequenceId, true);
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestScanner
org.apache.hadoop.hbase.regionserver.wal.TestLogRollingNoCluster
org.apache.hadoop.hbase.regionserver.wal.TestWALActionsListener
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13700//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13700//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13700//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13700//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13700//console
This message is automatically generated.
> 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)
