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/06/02 21:36:04 UTC

[jira] [Updated] (BOOKKEEPER-1092) Ledger Recovery - Add Test Case for Parallel Ledger Recovery

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

Sijie Guo updated BOOKKEEPER-1092:
----------------------------------
    Summary: Ledger Recovery - Add Test Case for Parallel Ledger Recovery  (was: Ledger Recovery - parallel ledger metadata update with bookie entries recovery proceedure)

> Ledger Recovery - Add Test Case for Parallel Ledger Recovery
> ------------------------------------------------------------
>
>                 Key: BOOKKEEPER-1092
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1092
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-client
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.5.0
>
>
> bookkeeper recovery improvement (part-5): parallel ledger metadata update with bookie entries recovery proceedure
>     currently, the ledger recovery procedure is
>     - read ledger metadata
>     - set ledger metadata to IN_RECOVERY state
>     - recover entries
>     - close ledger metadata.
>     as 'set ledger metadata to IN_RECOVERY' could be executed in parallel with 'recover entries'. this change is to explore this kind of parallelism.
>     RB_ID=266147



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)