commit | 6deb7f495a9111d5720e72dbc19a52ecbfd2557b | [log] [tgz] |
---|---|---|
author | Enrico Olivelli <eolivelli@gmail.com> | Tue Oct 20 16:36:31 2020 +0200 |
committer | GitHub <noreply@github.com> | Tue Oct 20 07:36:31 2020 -0700 |
tree | d638ae4a6d4ebd816ad0e8bdec64ba74957373fe | |
parent | 01214aa6d02ce55e4d20f47179b5e53c32617e85 [diff] |
BP-41 Bookie Address changes tracking - Allow the client to follow Bookie Address Changes - If a Bookie changes network address the clients will be able to connect to the new addresess - In order to leverage the most of this feature the Bookie must configure a fixed bookieId (see BP-41) - add flag enableBookieAddressTracking to enable/disable this feature, as it needs a ZK watch for every active bookie in the cluster and if you have a static cluster there is no need to invalidate the local cache and issue more ZK requests - handle ZK session expiration events, when the ZK client is not receiving watch notifications it could miss bookie address changes, so we have to eagerly flush the whole local cache of bookie addresses This is part of BP-41 Master ticket #2396 Reviewers: Nicolò Boschi <boschi1997@gmail.com>, Anup Ghatage <ghatage@apache.org> This closes #2435 from eolivelli/fix/bp41-client-discovery-cache
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.