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 2013/04/07 21:27:16 UTC
[jira] [Commented] (BOOKKEEPER-553) New LedgerManager for 64 Bits
Ledger ID Management in ZooKeeper
[ https://issues.apache.org/jira/browse/BOOKKEEPER-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625004#comment-13625004 ]
Sijie Guo commented on BOOKKEEPER-553:
--------------------------------------
BOOKKEEPER-590 is there to address the problem we might encounter using original SCAN-AND-COMPARE algorithm. as my comment in BOOKKEEPER-590, it would be better to provide another SCAN-AND-COMPARE algorithm rather than just remove the original one. it looks like we could have an interface in LedgerManager called #getGarbageCollector, which returns a GarbageCollector used by this ledger manager to do garbage collecting. so for the ledger manager here we could use the new SCAN-AND-COMPARE algorithm introduced in BOOKKEEPER-590.
> New LedgerManager for 64 Bits Ledger ID Management in ZooKeeper
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-553
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-553
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server, hedwig-server
> Reporter: Jiannan Wang
> Assignee: Jiannan Wang
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-553.patch, BOOKKEEPER-553.patch, BOOKKEEPER-553.patch, BOOKKEEPER-553.patch
>
>
> Once we extend the ledger id space to 64 bits, the 2-4-4 ledger id partition (see HierarchicalLedgerManager) is not suitable any more. So we need a new LedgerManager for 64 bits ledger id management in ZooKeeper.
--
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