hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pankaj Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-14449) Rewrite deadlock prevention for concurrent connection close
Date Wed, 16 Aug 2017 05:10:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128328#comment-16128328
] 

Pankaj Kumar edited comment on HBASE-14449 at 8/16/17 5:09 AM:
---------------------------------------------------------------

Sorry, by mistake assignee got modified. Have reverted back.


was (Author: pankaj2461):
Sorry, by mistake assignee got modified.

> Rewrite deadlock prevention for concurrent connection close
> -----------------------------------------------------------
>
>                 Key: HBASE-14449
>                 URL: https://issues.apache.org/jira/browse/HBASE-14449
>             Project: HBase
>          Issue Type: Bug
>          Components: master, metrics
>            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.4.14#64029)

Mime
View raw message