We are using 64 bit ledger ids internally right now, but the ledger id is supported by the application/caller. We have extended Hierarchical ledger manger to Long hierarchical ledger manger for this.
Ultimately we would like to move to 128 bit UUID as the ledger id. That makes ledgers unique without the need of centralized ZK/metadata server. On Tue, Oct 25, 2016 at 4:11 PM, Sijie Guo <si...@apache.org> wrote: > *Problem: * > > Currently the ledger id is long, which it should be 64-bits. However > currently bookkeeper only can generate 32-bits ledger id as zookeeper's > sequence znode only produce 32-bits. > > This problem was basically raised before at BOOKKEEPER-421. Jiannan has > already done fair amount of work on this and there were several patches for > it. > > This email thread is to start the discussion for 64-bits ledger id support > in bookkeeper. > > *Discuss*: > > Based on bookkeeper-421, the changes will relatively happen in following > places. Assume the metadata store is ZooKeeper. > > > 1. How to generate 64-bits ledger id? (64 Bits Ledger ID Generation > <https://issues.apache.org/jira/browse/BOOKKEEPER-552>) > 2. How to store the 64-bits ledger id in zookeeper? (New LedgerManager > for 64 Bits Ledger ID Management in ZooKeeper > <https://issues.apache.org/jira/browse/BOOKKEEPER-553>) > 3. How can the garbage collect handle correctly with 64-bits ledger id? > ( > https://issues.apache.org/jira/browse/BOOKKEEPER-553? > focusedCommentId=13558192&page=com.atlassian.jira. > plugin.system.issuetabpanels:comment-tabpanel#comment-13558192 > ) > 4. How can we upgrade current HierarchicalLedgerManager to support > 64-bits. [??] > > Feel free to take a look at those tickets and make any proposals. > > - Sijie > -- Jvrao --- First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi
