[
https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741504#comment-14741504
]
stack commented on HBASE-12751:
-------------------------------
All this fails:
2015-09-11 13:08:01.896 Vim[4556:17136812] Can't allocate a new block for a
pasteboard. Creation of a new Pasteboard will fail.
kalashnikov:hbase.git stack$ python dev-support/findHangingTests.py
https://builds.apache.org/job/PreCommit-HBASE-Build/15564//consoleText
Fetching the console output from the URL
Printing hanging tests
Hanging test : org.apache.hadoop.hbase.replication.TestMasterReplication
Hanging test : org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol
Hanging test : org.apache.hadoop.hbase.master.handler.TestCreateTableHandler
Hanging test : org.apache.hadoop.hbase.TestIOFencing
Hanging test :
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint
Hanging test : org.apache.hadoop.hbase.snapshot.TestFlushSnapshotFromClient
Hanging test : org.apache.hadoop.hbase.master.TestDistributedLogSplitting
Hanging test : org.apache.hadoop.hbase.io.hfile.TestHFileBlock
Hanging test :
org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer
Hanging test :
org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures
Hanging test : org.apache.hadoop.hbase.io.hfile.TestScannerSelectionUsingTTL
Hanging test : org.apache.hadoop.hbase.master.procedure.TestServerCrashProcedure
Hanging test : org.apache.hadoop.hbase.master.TestAssignmentManagerOnCluster
Hanging test : org.apache.hadoop.hbase.master.snapshot.TestSnapshotFileCache
Hanging test : org.apache.hadoop.hbase.master.TestMasterFailover
Hanging test : org.apache.hadoop.hbase.regionserver.TestMultiColumnScanner
Hanging test : org.apache.hadoop.hbase.regionserver.TestRegionReplicaFailover
Hanging test :
org.apache.hadoop.hbase.replication.regionserver.TestReplicationWALReaderManager
Hanging test :
org.apache.hadoop.hbase.master.balancer.TestStochasticLoadBalancer2
Hanging test : org.apache.hadoop.hbase.io.hfile.TestCacheOnWrite
Hanging test :
org.apache.hadoop.hbase.regionserver.compactions.TestCompactionWithThroughputController
Hanging test : org.apache.hadoop.hbase.master.TestMasterShutdown
Hanging test :
org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay
Hanging test : org.apache.hadoop.hbase.snapshot.TestExportSnapshot
Hanging test : org.apache.hadoop.hbase.regionserver.TestRegionReplicas
Printing Failing tests
Failing test : org.apache.hadoop.hbase.client.TestFastFail
Failing test :
org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS
> 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, 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)
