[
https://issues.apache.org/jira/browse/BOOKKEEPER-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483373#comment-13483373
]
Ivan Kelly commented on BOOKKEEPER-346:
---------------------------------------
I dont like the coupling of the journal with ledger storage. It makes things
hard to test and benchmark in isolation. Whats more, it's unnecessary.
If we have the copy sequence as above
1) copy A.idx to A.idx.rloc
2) delete A.idx
3) rename A.idx.rloc to A.idx
the problematic case is if we crash after 2, before 3 completes. But if on
initialization of the LedgerCacheImpl, we scan all directories for A.idx.rloc,
if A.idx exists the copy was incomplete, remove A.idx.rloc, if A.idx does not
exist, rename A.idx.rloc to A.idx. Theres no need to mess with the journal at
all.
> Detect IOExceptions in LedgerCache and bookie should look at next ledger
> dir(if any)
> ------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-346
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-346
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Affects Versions: 4.1.0
> Reporter: Rakesh R
> Assignee: Vinay
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-346.patch, BOOKKEEPER-346.patch,
> BOOKKEEPER-346.patch, BOOKKEEPER-346.patch, BOOKKEEPER-346.patch,
> BOOKKEEPER-346.patch
>
>
> This jira to detect IOExceptions in "LedgerCache" to iterate over all the
> configured ledger(s).
--
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
