[
https://issues.apache.org/jira/browse/BOOKKEEPER-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725548#comment-14725548
]
Venkateswararao Jujjuri commented on BOOKKEEPER-864:
----------------------------------------------------
Thanks for your insights on this issue Sijie. I understand backward
compatibility is critical.
We will think through this more and if needed will do a spike.
Thanks,
JV
> 128 bit LedgerId
> ----------------
>
> Key: BOOKKEEPER-864
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-864
> Project: Bookkeeper
> Issue Type: Improvement
> Reporter: Venkateswararao Jujjuri
>
> BookKeeper coordinates with ZooKeeper to generate an cluster wide LedgerId.
> This is a 64 bit number. This method works great because we have ZK acting as
> a centralized coordinator. But this method may not scale as the cluster size
> and number of ledgers increase.
> GUIDs ( (https://en.wikipedia.org/wiki/Globally_unique_identifier) are
> preferred way to generate decentralized globally unique IDs and it takes 128
> bits ; This method can scale well as it doesn’t need a centralized
> coordination.
> Current BK code used ledgerId as a primary object, any change to this (64
> to128 bit) warrants across the board code changes.
> Opening this issue so we can solicit community input and track the progress.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
