[
https://issues.apache.org/jira/browse/HBASE-20949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558337#comment-16558337
]
Duo Zhang commented on HBASE-20949:
-----------------------------------
{noformat}
2018-07-26 11:58:08,573 DEBUG [PEWorker-1]
assignment.RegionTransitionProcedure(436): LOCK_EVENT_WAIT pid=123
serverLocks={}, namespaceLocks={},
tableLocks={{testRestoreSnapshotAfterSplittingRegions-1532606269310=exclusiveLockOwner=121,
sharedLockCount=-8, waitingProcCount=0}},
regionLocks={{d203b8d2c63118f256573f525e6edc8c=exclusiveLockOwner=117,
sharedLockCount=0, waitingProcCount=0},
{f45f7e4b5c5d68e47af5c23908cb3818=exclusiveLockOwner=127, sharedLockCount=0,
waitingProcCount=0}, {b7b3607bb9c1483a16637cac9fac1719=exclusiveLockOwner=120,
sharedLockCount=0, waitingProcCount=1}}, peerLocks={}, metaLocks={}
{noformat}
We have this, obviously we have something wrong with sharedLockCount, it is -8.
Let me dig more.
> Split/Merge table can be executed concurrently with DisableTableProcedure
> -------------------------------------------------------------------------
>
> Key: HBASE-20949
> URL: https://issues.apache.org/jira/browse/HBASE-20949
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Priority: Major
>
> The top flaky tests on the dashboard are all because of this.
> TestRestoreSnapshotFromClient
> TestSimpleRegionNormalizerOnCluster
> Theoretically this should not happen, need to dig more.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
