[
https://issues.apache.org/jira/browse/HBASE-14268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710014#comment-14710014
]
Ted Yu commented on HBASE-14268:
--------------------------------
>From https://builds.apache.org/job/PreCommit-HBASE-Build/15214/console :
{code}
Flaked tests:
org.apache.hadoop.hbase.util.TestWeakObjectPool.testWeakReference(org.apache.hadoop.hbase.util.TestWeakObjectPool)
Run 1: TestWeakObjectPool.testWeakReference:81 expected:<0> but was:<1>
Run 2: TestWeakObjectPool.testWeakReference:81 expected:<0> but was:<1>
Run 3: PASS
{code}
The above can be reproduced locally.
> Improve KeyLocker
> -----------------
>
> Key: HBASE-14268
> URL: https://issues.apache.org/jira/browse/HBASE-14268
> Project: HBase
> Issue Type: Improvement
> Components: util
> Reporter: Hiroshi Ikeda
> Assignee: Hiroshi Ikeda
> Priority: Minor
> Attachments: HBASE-14268-V2.patch, HBASE-14268-V3.patch,
> HBASE-14268-V4.patch, HBASE-14268.patch, KeyLockerPerformance.java
>
>
> 1. In the implementation of {{KeyLocker}} it uses atomic variables inside a
> synchronized block, which doesn't make sense. Moreover, logic inside the
> synchronized block is not trivial so that it makes less performance in heavy
> multi-threaded environment.
> 2. {{KeyLocker}} gives an instance of {{RentrantLock}} which is already
> locked, but it doesn't follow the contract of {{ReentrantLock}} because you
> are not allowed to freely invoke lock/unlock methods under that contract.
> That introduces a potential risk; Whenever you see a variable of the type
> {{RentrantLock}}, you should pay attention to what the included instance is
> coming from.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
