[
https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902858#comment-14902858
]
stack commented on HBASE-12751:
-------------------------------
Has these as hanging:
kalashnikov:hbase.git stack$ python ./dev-support/findHangingTests.py
https://builds.apache.org/job/PreCommit-HBASE-Build/15664//consoleText
Fetching the console output from the URL
Printing hanging tests
Hanging test : org.apache.hadoop.hbase.client.TestMobCloneSnapshotFromClient
Hanging test : org.apache.hadoop.hbase.client.TestReplicasClient
Hanging test : org.apache.hadoop.hbase.regionserver.TestHRegion
Hanging test : org.apache.hadoop.hbase.namespace.TestNamespaceAuditor
Hanging test : org.apache.hadoop.hbase.TestAcidGuarantees
Hanging test : org.apache.hadoop.hbase.TestZooKeeper
Printing Failing tests
Trying all tests locally and they pass. Looking at failures up in jenkins.....
For TestZooKeeper... it is an interesting one... seems unrelated though:
{code}
2015-09-22 08:54:42,962 INFO [RS:0;asf906:46174]
regionserver.HRegionServer(1099): stopping server
asf906.gq1.ygridcore.net,46174,1442912078095; zookeeper connection closed.
2015-09-22 08:54:42,962 INFO [RS:0;asf906:46174]
regionserver.HRegionServer(1102): RS:0;asf906:46174 exiting
2015-09-22 08:54:42,962 ERROR [SyncThread:0] server.NIOServerCnxn(178):
Unexpected Exception:
java.nio.channels.CancelledKeyException
at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73)
at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:77)
at
org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:151)
at
org.apache.zookeeper.server.NIOServerCnxn.sendResponse(NIOServerCnxn.java:1081)
at
org.apache.zookeeper.server.NIOServerCnxn.process(NIOServerCnxn.java:1118)
at
org.apache.zookeeper.server.WatchManager.triggerWatch(WatchManager.java:120)
at
org.apache.zookeeper.server.WatchManager.triggerWatch(WatchManager.java:92)
at org.apache.zookeeper.server.DataTree.deleteNode(DataTree.java:591)
at org.apache.zookeeper.server.DataTree.processTxn(DataTree.java:802)
at
org.apache.zookeeper.server.ZKDatabase.processTxn(ZKDatabase.java:329)
at
org.apache.zookeeper.server.ZooKeeperServer.processTxn(ZooKeeperServer.java:994)
at
org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:116)
at
org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:200)
at
org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:131)
{code}
I went through all the others and nothing untoward. Let me retry.
> 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, 12751.v40.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)
