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

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/10/10 18:53:42 UTC

[jira] [Updated] (BOOKKEEPER-658) ledger cache refactor

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

Ivan Kelly updated BOOKKEEPER-658:
----------------------------------

    Attachment: 0001-BOOKKEEPER-658-ledger-cache-refactor.patch

I had to refactor a bit and add BOOKKEEPER-604. 

+1 on the patch from me. One question though, the in memory manager has a handle on the persistent manager. Why not have it make the calls on persistent manager, rather than calling both from LedgerCacheImpl?

> ledger cache refactor
> ---------------------
>
>                 Key: BOOKKEEPER-658
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-658
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-server
>            Reporter: Sijie Guo
>            Assignee: Robin Dhamankar
>             Fix For: 4.3.0
>
>         Attachments: 0001-BOOKKEEPER-658-ledger-cache-refactor.patch, BOOKKEEPER-658.patch
>
>
> refactor ledger cache to separate in-memory page management from persistent management.



--
This message was sent by Atlassian JIRA
(v6.1#6144)