[
https://issues.apache.org/jira/browse/BOOKKEEPER-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433041#comment-13433041
]
surendra singh lilhore commented on BOOKKEEPER-326:
---------------------------------------------------
@Ivan
Jcarder Report without applying the patch :
========================================================================
Opening for reading: D:\out\jcarder_contexts.db
Opening for reading: D:\out\jcarder_events.db
Loaded from database files:
Nodes: 843
Edges: 774 (excluding 10449 duplicated)
Cycle analysis result:
Cycles: 1
Edges in cycles: 2
Nodes in cycles: 2
Max cycle depth: 2
Max graph depth: 3
Ignoring 0 gated cycle(s).
Ignoring 0 almost identical cycle(s).
===================================================================================
Here one cycle is found.
I have attached one BK326.PNG file which show the graphically Deadlock cycle.
> 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: BK326.png, BK_DeadLock.log, BOOKKEEPER-326.1.patch,
> BOOKKEEPER-326.2.patch, BOOKKEEPER-326.3.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
