commit | 8502c2e461f58162a3e498f093a49d4e2eb253f3 | [log] [tgz] |
---|---|---|
author | Nicolò Boschi <boschi1997@gmail.com> | Mon Sep 21 11:44:58 2020 +0200 |
committer | GitHub <noreply@github.com> | Mon Sep 21 11:44:58 2020 +0200 |
tree | ec11eaa96ca85b6744adab16f4b12f4856749cba | |
parent | a432865dd6e9d5096b0ec0c1ac8cd5862068a366 [diff] |
Spammy log when one bookie of ensemble is down #2285 Descriptions of the changes in this PR: ### Motivation Resolves #2285 ### Changes We write "bookie server unavailable log" every 30 seconds per bookie client Reviewers: Enrico Olivelli <eolivelli@apache.org, Sijie Guo <sijie@apache.org> This closes #2393 from nicoloboschi/fix/2285/spammy-logs, closes #2285
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.