You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2017/07/28 00:03:00 UTC

[jira] [Resolved] (BOOKKEEPER-754) Bookie: flush ledger storage after replaying journal

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sijie Guo resolved BOOKKEEPER-754.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 4.5.0)

It was merged with other changes.

> Bookie: flush ledger storage after replaying journal
> ----------------------------------------------------
>
>                 Key: BOOKKEEPER-754
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-754
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>
> we need to optimize the bookie startup logic for the case: if a bookie failed after replaying journal again and again.
> - start syncthread before replaying journal, so during journal replaying, the ledger storage could be checkpoint/flushed.
> - after journal finished replaying, trigger a fully flush on ledger storage.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)