[
https://issues.apache.org/jira/browse/BOOKKEEPER-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872771#comment-15872771
]
ASF GitHub Bot commented on BOOKKEEPER-552:
-------------------------------------------
Github user knusbaum commented on the issue:
https://github.com/apache/bookkeeper/pull/112
LongHierarchicalLedgerManager is being moved to HierarchicalLedgerManager
and HierarchicalLedgerManager is being moved to LegacyHierarchicalLedgerManager.
LongHierarchicalLedgerManager (now HierarchicalLedgerManager) has been made
backwards-compatible so that existing Bookkeeper instances running
HierarchicalLedgerManager can be upgraded to the new code, which will allow
64-bit IDs.
This is achieved by having the HierarchicalLedgerManager proxy requests to
the LegacyHierarchicalLedgerManager for ids which are less than
Integer.MAX_VALUE
For ids greater than that, the new code is used.
We also add a new id generator. The existing ZkLedgerIdGenerator is limited
to 31 bits (about 2 million) ledgers because ZooKeeper's sequential id
generator uses a signed int internally. IDs start going negative if you
overflow it, which messes some stuff up.
The new ID generator uses a multi-level directory scheme to overcome this.
> 64 Bits Ledger ID Generation
> ----------------------------
>
> Key: BOOKKEEPER-552
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-552
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server, hedwig-server
> Reporter: Jiannan Wang
> Assignee: Kyle Nusbaum
> Attachments: BOOKKEEPER-552.patch, BOOKKEEPER-552.patch,
> BOOKKEEPER-552.patch
>
>
> This task aims to find and implement 64 bits global unique ledger id
> generation mechanisms.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
