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

Sijie Guo commented on BOOKKEEPER-326:
--------------------------------------

ah, sorry, I just missed the part you move from #connect() to 
#connectIfNeededAndDoOp(). you changes are correct.

>> BTW, if you have any suggestions/logic to be done as part of this JIRA, 
>> could you please explain me so that I'll take care

I don't have any logic to add here. As my comment, if we want to change 
throttling mechanism, it would be in BOOKKEEPER-239 not here.

+1 on Rakesh's changes.
                
> 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

        

Reply via email to