[
https://issues.apache.org/jira/browse/BOOKKEEPER-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715435#comment-13715435
]
Sijie Guo commented on BOOKKEEPER-655:
--------------------------------------
this should be addressed by BOOKKEEPER-604. Vinay, please confirm. if it is,
please mark this as duplicated.
> Race between addEntry and deleteLedger causes all further flushes to fail
> -------------------------------------------------------------------------
>
> Key: BOOKKEEPER-655
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-655
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.2.1, 4.3.0
> Reporter: Vinay
> Assignee: Vinay
> Attachments: BOOKKEEPER-655.patch
>
>
> In One of our cluster, following has been found.
> 1. One simple program to create ledgers, read and delete ledger will be
> running periodically to check the service availability.
> 2. At one point, one of the Bookie got timeout while adding entry, and
> program executed with other bookies, did add,read and delete of ledger.
> 3. In the timed out bookie, there was a race created between addEntry and
> delete entry in LedgerCacheImpl and it caused all further flushes to fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
