commit | bbb0113d61d3c4c47079f5924ad00bc433925b63 | [log] [tgz] |
---|---|---|
author | karanmehta93 <k.mehta@salesforce.com> | Tue Nov 03 02:03:44 2020 -0800 |
committer | GitHub <noreply@github.com> | Tue Nov 03 18:03:44 2020 +0800 |
tree | 5468957c94f4afa38673d2225bcc270f37b7f0d6 | |
parent | c1673bfc140b2a3c2636cfae91c26869e6cf9502 [diff] |
Introduce new retry policy for metadata operations (#2470) Descriptions of the changes in this PR: ### Motivation Current retry backoff policy is truly exponential, hence retries are spaced out at large intervals. There is maxBackOff time that limits it, but it doesn't have a concept of deadline. Hence, applications with shorter SLA's have issues dealing with ZK failures and recovering from it. ### Changes The new policy introduces an aggressive retry mechanism with the backoff constants as less exponential. The deadline ensures that we retry at least once at the deadline. The stack trace would indicate the operation at risk. This doesn't update the product code, which is still in testing. I am splitting PR's for for sake of reviews. * Introduce new retry policy for metadata operations * Spotbugs error fix
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.