[
https://issues.apache.org/jira/browse/BOOKKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-326:
----------------------------------
Attachment: BOOKKEEPER-326.part2.diff
I managed to repro this.
I think the solution should be two-fold.
1. We should tighten up the the synchronization as Rakesh's patch does.
2. We should ensure that call to the client don't reenter. I've attached a
patch which insures it doesn't happen on the public methods of LedgerHandle.
In fact, I think 1 could go even further. The only thing that needs to be
protected by synchronization in PerChannelBookieClient#connect is the state
variable. As such, that's all we should be protecting.
> 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.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
