Vanlightly opened a new issue #2908: URL: https://github.com/apache/bookkeeper/issues/2908
Ledger recovery counts on bookies to respond with OK or an error when a client performing recovery reads an entry that was previously acknowledged to the original client. If a bookie responds with a NoSuchEntry or NoSuchLedger for such an entry, then recovery may close the ledger at that point, truncating it (data loss). The EntryLogger can throw a NoEntryException if a log file is corrupted, thus leaving BookKeeper vulnerable to ledger truncation when a log file gets corrupted, turning a recoverable data loss situation into an unrecoverable data loss. PR coming. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
