You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Ian Dimayuga (JIRA)" <ji...@apache.org> on 2014/10/14 20:03:33 UTC

[jira] [Updated] (ZOOKEEPER-2060) Deadlock in NettyServerCnxnFactory

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Dimayuga updated ZOOKEEPER-2060:
------------------------------------
    Attachment: ZOOKEEPER-2060_deadlock_jstack.txt

Attached: jstack result while server is blocked.

> Deadlock in NettyServerCnxnFactory
> ----------------------------------
>
>                 Key: ZOOKEEPER-2060
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2060
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.6, 3.5.0
>            Reporter: Ian Dimayuga
>            Assignee: Ian Dimayuga
>             Fix For: 3.4.7, 3.5.1
>
>         Attachments: ZOOKEEPER-2060_deadlock_jstack.txt
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> In NettyServerCnxnFactory, high throughput triggers a deadlock.
> This is caused by a channel-buffer-dumping debug statement in NettyServerCnxnFactory.java that is executed regardless of log level.
> This code path only executes when the server is throttling, but when it does it encounters a race and occasional deadlock between the channel buffer and NettyServerCnxn (jstack attached).
> The proposed fix adds the debug logging guard to this statement, similar to other existing statements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)