[
https://issues.apache.org/jira/browse/HBASE-25809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell updated HBASE-25809:
----------------------------------------
Description:
TestAtomicOperation.testMultiRowMutationMultiThreads deadlocks.
There is an easy fix for the test that synchronizes on the CHM instead of the
object. We already have a Findbugs exceptions for synchronization on the CHM
and get-then-set on it is what we synchronizing for anyway.
This is only relevant for branch-1 because we have to synchronize get-then-set
due to Java 7 compatibility. For branch-2 and master we use
CHM#computeIfPresent.
was:
TestAtomicOperation.testMultiRowMutationMultiThreads deadlocks.
There is an easy fix for the test that synchronizes on the CHM instead of the
object. We already have a Findbugs exceptions for synchronization on the CHM
and get-then-set on it is what we synchronizing for anyway.
> [branch-1] TestAtomicOperation.testMultiRowMutationMultiThreads deadlock
> ------------------------------------------------------------------------
>
> Key: HBASE-25809
> URL: https://issues.apache.org/jira/browse/HBASE-25809
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 1.7.0
>
>
> TestAtomicOperation.testMultiRowMutationMultiThreads deadlocks.
> There is an easy fix for the test that synchronizes on the CHM instead of the
> object. We already have a Findbugs exceptions for synchronization on the CHM
> and get-then-set on it is what we synchronizing for anyway.
> This is only relevant for branch-1 because we have to synchronize
> get-then-set due to Java 7 compatibility. For branch-2 and master we use
> CHM#computeIfPresent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
