| commit | 7645cb839761b9dde6462c28a87a0d1c428bf5fa | [log] [tgz] |
|---|---|---|
| author | hangc0276 <hangc0276@163.com> | Thu Aug 13 16:43:48 2020 +0800 |
| committer | GitHub <noreply@github.com> | Thu Aug 13 01:43:48 2020 -0700 |
| tree | 72b7681b38c9815eb60ee0a26b6d6048af36da27 | |
| parent | 62f3cd0e60bb5f9e17442512914fa88447932d43 [diff] |
Bookie Client add quarantine ratio when error count exceed threshold ### Motivation When bookie client read/write data from/to bookie servers, it will check the health of each connected server in sepecific interval. Once the amount of errors reached the threshold, the bookie server will be quarantined for server miniutes (configurated by `bookieQuarantineTimeSeconds`) by the bookie client. In most circumstance, there are large amount of bookie clients connected to one bookie server, like pulsar broker. Once the bookie server runs in heavy load, most of bookie clients will receive errors and trigger quarantine in the same time, and then quarantine the server for several miniutes. After a few miniutes passed by, the quarantined server will be put back in the same time for most bookie clients, which will lead to periodic oscillation of in/out throughput of the server. It is the obstacle of tunning the throughput of the bookkeeper cluster. ### Changes I introduce a quarantine probability to determine whether to quarantine the server for the client, avoiding quaraninte the heavy load server in the same time for most of bookie client. I also expose the quarantine stats to prometheus. Reviewers: Jia Zhai <zhaijia@apache.org>, Sijie Guo <None> This closes #2327 from hangc0276/bookieClient_Quarantine_ratio
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.