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/05/06 14:54:15 UTC

[jira] [Updated] (BOOKKEEPER-608) Make SyncThread a reusable component

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

Ivan Kelly updated BOOKKEEPER-608:
----------------------------------

    Attachment: 0001-BOOKKEEPER-608-Move-syncthread-out-of-bookie.patch

Patch moves the syncthread code into its own class. Bookie still owns the instance, but creates it by passing in the LedgerStorage and CheckpointSource.
                
> Make SyncThread a reusable component
> ------------------------------------
>
>                 Key: BOOKKEEPER-608
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-608
>             Project: Bookkeeper
>          Issue Type: Sub-task
>          Components: bookkeeper-server
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.3.0
>
>         Attachments: 0001-BOOKKEEPER-608-Move-syncthread-out-of-bookie.patch
>
>
> The sync thread is currently a inner class of Bookie. This means it's not possible to test the functionality of the sync thread and ledger storage without creating a full bookie, and when you do that you also have to create a journal etc. 

--
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