[
https://issues.apache.org/jira/browse/HBASE-14449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876740#comment-14876740
]
Hudson commented on HBASE-14449:
--------------------------------
SUCCESS: Integrated in HBase-1.1 #666 (See
[https://builds.apache.org/job/HBase-1.1/666/])
HBASE-14449 Rewrite deadlock prevention for concurrent connection close (tedyu:
rev 05618091b8f488e5b2ff81372cac2df11fd6e0d9)
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java
> Rewrite deadlock prevention for concurrent connection close
> -----------------------------------------------------------
>
> Key: HBASE-14449
> URL: https://issues.apache.org/jira/browse/HBASE-14449
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.0.3, 1.1.3
>
> Attachments: 14449-branch-1.0.txt, 14449-v1.txt
>
>
> The deadlock prevention approach used in HBASE-14241 introduces unnecessary
> logic which is not intuitive.
> Depending on the value for config hbase.ipc.client.specificThreadForWriting ,
> there may or may not be CallSender threads running.
> The attached patch simplifies deadlock prevention by using a Set which
> represents the Connections to be closed. Outside the synchronized
> (connections) block, this Set is iterated where the Connections are closed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
