[
https://issues.apache.org/jira/browse/BOOKKEEPER-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958909#comment-13958909
]
Flavio Junqueira commented on BOOKKEEPER-710:
---------------------------------------------
bq. I think readLastAddConfirmed is just a broken api
I've just noticed some of the comments here, in particular this one. Is there a
jira for this or this just a rant?
bq. might have idea on how many watches zookeeper can sustain.
It is mainly memory, but triggering many watches at a time also causes a burst
of notifications. I can't think of anything else right now.
I was also wondering if there is a jira for these todos:
{noformat}
// TODO: should provide ledger metadata listener in metadata store.
{noformat}
Also, do we really have to wait 5 seconds in the test to make sure that the
call doesn't get stuck?
{noformat}
TimeUnit.SECONDS.sleep(5);
{noformat}
> OpenLedgerNoRecovery should watch ensemble change.
> --------------------------------------------------
>
> Key: BOOKKEEPER-710
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-710
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Priority: Blocker
> Fix For: 4.3.0, 4.2.3
>
> Attachments:
> 0001-BOOKKEEPER-710-OpenLedgerNoRecovery-should-watch-ens.patch,
> BOOKKEEPER-710.diff
>
>
> LedgerHandle opened by openLedgerNoRecovery should watch ensemble change.
> otherwise, readLastConfirmed & readEntries will stuck if there are ensemble
> changes in the ledger.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
