eolivelli commented on issue #1580: (@bug W-5100764@) Write Ledger Handle listens for metadata changes URL: https://github.com/apache/bookkeeper/pull/1580#issuecomment-410811838 @sijie this is a very different use case from your experience with huge systems. The case in which that watch is not very useful is this: - You have in the cluster only 1 or 2 bookies. - You are using BK for storing blobs for cery long time. So you are never hitting ensemble changes, no automatic re-replication (only manual and in case of bad errors). Ledgers metadata are very cold, they necwr change, so that watch will not be useful. If you are randomly opening many ledgers and the closing them, you will create a lot of useless watches. You can make many optimizations, like keeping open ledger handles in a cache, but those watches will have a cost and can be saved. For the case in which there is an ensemble change the reader ledger handle can be reopened so that metadata are reread. I will start another email thread, this is a bit off topic here
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
