commit | c31dff9ff8dc3ec7454a62d71a9fff2af8505ee9 | [log] [tgz] |
---|---|---|
author | Masahiro Sakamoto <massakam@yahoo-corp.jp> | Sun Jul 31 16:12:06 2022 +0900 |
committer | GitHub <noreply@github.com> | Sun Jul 31 15:12:06 2022 +0800 |
tree | 5ff60a5b334d7ff1899e65f33cd9c22fb0a1aeac | |
parent | f06800c02ea5045de21c115dee9c68a5a5759434 [diff] |
BP-41 Add flag to enable/disable BookieAddressResolver (#3356) ### Motivation With BP-41, the BookKeeper client now needs a request to ZooKeeper to resolve the address from each bookie ID. In the following document, there is a description of the flag ~`enableBookieAddressResolver`~ `bookieAddressResolverEnabled` for disabling this feature by regarding the bookie ID as an address or hostname, but it seems that this has not been implemented yet. https://github.com/apache/bookkeeper/blob/master/site3/website/src/pages/bps/BP-41-bookieid.md I implemented this because I want this flag to reduce the number of requests to ZK. ### Changes Added a flag named ~`enableBookieAddressResolver`~ `bookieAddressResolverEnabled` to the client configuration. If this flag is false, use `BookieAddressResolverDisabled` instead of `DefaultBookieAddressResolver` as the address resolver for bookies. `BookieAddressResolverDisabled` regards a bookie ID to be in legacy format, i.e. "address:port" or "hostname:port", and returns the address of that bookie without access to ZK. Master Issue: #2396
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:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue.
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 our installation guide to get your local environment setup.
Take a look at our open issues: Github Issues.
Review our coding style and follow our pull requests to learn more about our conventions.
Make your changes according to our contributing guide