[
https://issues.apache.org/jira/browse/BOOKKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429993#comment-13429993
]
Ivan Kelly commented on BOOKKEEPER-326:
---------------------------------------
I think it's near impossible to automatically and reliably trigger this
deadlock, as it's reliant on a delay occurring between bootstrap.connect, and
adding the FutureListener. I think I could get it to trigger fairly reliably
with some hacks in the code (no suitable for putting into production), so you
you submit a patch with the fix, forgetting about the test case, run with the
hack to ensure it hits, apply your patch, and then run with the hack again to
verify the deadlock does not occur.
> 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
> Assignee: Rakesh R
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: BK_DeadLock.log, BOOKKEEPER-326.1.patch,
> BOOKKEEPER-326.2.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
