[
https://issues.apache.org/jira/browse/BOOKKEEPER-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907691#comment-14907691
]
Sijie Guo commented on BOOKKEEPER-873:
--------------------------------------
What tests you were running? it would be better to provide your test case and
your log. so other people could reproduce and help on it.
re > Sometimes I can't find the entry I wrote.
Did you ever using same ledger id: delete it and re-create ledger id again? It
would cause correctness issue if in the whole life cycle of the cluster there
are two ledgers created with same ledger id. because the ledger's data is
garbage collected lazily after a ledger is deleted.
re > BadVersion
My suspect is same as above that there is two ledger handle with same ledger id
that is accessing ledger medata at the same time. You should attach the log
that contains more information.
btw, just by inspecting the code, the code change in FlatLedgerManager breaking
backward compatibility:
https://github.com/jvrao/bookkeeper/commit/c1b7379301d791eb1c8f4bafd67b25d698a82ae3#diff-9870817a8370de06472db261d2773fddL67
Also, you would be better to use HierarchicalLedgerManager rather than
FlatLedgerManager. it would scale with increased number of ledgers.
> Enhance CreatedLedger API to accept ledgerId as input
> -----------------------------------------------------
>
> Key: BOOKKEEPER-873
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-873
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client
> Affects Versions: 4.3.1
> Reporter: Venkateswararao Jujjuri
> Assignee: Venkateswararao Jujjuri
> Fix For: 4.4.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
