commit | edffdd6dc261c3a9222751187a9f5ac601e9b1fa | [log] [tgz] |
---|---|---|
author | Andras Beni <andras.beni@streamnative.io> | Mon Mar 21 16:06:01 2022 +0100 |
committer | GitHub <noreply@github.com> | Mon Mar 21 08:06:01 2022 -0700 |
tree | a3bb388f573e1da61a5f9669111c44ed4db6c43b | |
parent | 7bb0bfcafbfb7cb2ee330707e082f27c3a8fd530 [diff] |
Log NoLedgerException on debug level (#3117) NoLedgerException does not signify an error in the Bookie that needs to be fixed. Instead it is - at most - a user error that the user is notified about via the status code ENOLEDGER. Logging this problem at error level introduces an odd difference between the behavior of readLac using v2 versus v3 protocol version. In the former case ReadEntryProcessor logs the same problem at debug level. As a result changing protocol version appers to be introducing an error.
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