[
https://issues.apache.org/jira/browse/BOOKKEEPER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431783#comment-13431783
]
Sijie Guo commented on BOOKKEEPER-356:
--------------------------------------
I don't have same options to close them. I think these jiras might be created
due to some problems. so I just delete them. Also BOOKKEEPER-356 is a weird
jira too. it doesn't have any option to submit patch or close it.
> Ledger will never recover if one of the quorum bookie is down forever and
> others dont have entry
> ------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-356
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-356
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Vinay
> Priority: Minor
>
> As discussed in BOOKKEEPER-355, current fix to handle the below issue is not
> correct. Need to find out new solution
> If some bookies of a quorum gone forever, some bookies of this quorum are
> still alive but doesn't have that entry (NoSuchEntry or NoSuchLedger), then
> the ledger doesn't have any evidence to recovery/close it.
--
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
