[
https://issues.apache.org/jira/browse/BOOKKEEPER-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966330#comment-13966330
]
Flavio Junqueira commented on BOOKKEEPER-710:
---------------------------------------------
About the question on watches, I knew I had looked into it, but I couldn't
remember where the discussion. In Chapter 4 of the ZK book, there is a
discussion about the scalability of watches. Each new watch consumes around 300
bytes on the server, so again watches induce memory utilization on the server
and possibly bursts of traffic depending on the number of notifications
triggered. One way to spread watches across servers is to use observers
> 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)
