[
https://issues.apache.org/jira/browse/BOOKKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414963#comment-13414963
]
Rakesh R commented on BOOKKEEPER-326:
-------------------------------------
Thanks a lot Ivan for your time:)
I've uploaded new patch by incorporating Ivan's point. Here I tried to keep
only the 'state' and 'channel' under the PerChannelBookieClient.this lock.
Also, I've added a test case but this will only forcing to establish new client
connections. With this there is high chance of getting notifications in the
same thread and invoke the pending operations in the caller thread itself. We
would be able to reproduce the deadlock scenario only by putting debug points.
Hi others, Please have a look on the latest patch.
Thanks,
Rakesh
> DeadLock during ledger recovery
> --------------------------------
>
> Key: BOOKKEEPER-326
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-326
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.1.0
> Reporter: Vinay
> Priority: Blocker
> Attachments: BK_DeadLock.log, BOOKKEEPER-326.1.patch,
> BOOKKEEPER-326.part2.diff, BOOKKEEPER-326.patch
>
>
> Deadlock found during ledger recovery. please find the attached thread dump.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
