[
https://issues.apache.org/jira/browse/BOOKKEEPER-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh R updated BOOKKEEPER-686:
--------------------------------
Attachment: 0003-BOOKKEEPER-686.patch
> Bookie startup will fail if one of the configured ledgerDir is full and the
> same is used for replaying the journal
> ------------------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-686
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-686
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.2.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 00001-BOOKKEEPER-686-trunk.patch,
> 00002-BOOKKEEPER-686-trunk.patch, 0003-BOOKKEEPER-686.patch
>
>
> When bookie startup, entry logger is randomly picking one of the configured
> ledger directory and creates a new log to write. Now journal will be
> replaying the entries and add to the entry logger.
> Unfortunately, if the randomly selected ledger directory is full, then it
> will immediately fail the bookie startup. Here Bookie is not efficiently
> filtering the writable ledger directories and utilizing all the available
> ledger directories.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
