commit | 9bb7e4b8245507ce1aefc9ff9a316c1407016240 | [log] [tgz] |
---|---|---|
author | Venkateswararao Jujjuri (JV) <jujjuri@gmail.com> | Tue Apr 30 20:20:32 2019 -0700 |
committer | GitHub <noreply@github.com> | Tue Apr 30 20:20:32 2019 -0700 |
tree | b933d2e23581413976aa95047bce0e45b514f53b | |
parent | bd699e61d729f327b5de302089d11bc3dcadfeb8 [diff] |
Explicit error message if extent is not present on ZK (#2066) * Explicit error message if extent is not present on ZK Client can get no extent error in the following two scenarios. 1. When client attempted to read/open an extent that is not on ZK (metadata server) 2. When client attempted to read a Ledger which is on metadata server, but somehow missing on bookies (Data server) It is quite confusing to get the same error, NoSuchLedgerExists for both these cases. This checkin introduced a new error at the BookKeeper client level, NoSuchLedgerExistsOnMetadataServer if it is not available on ZK. For errors related to Ledger is not available on bookie, I left NoSuchLedgerExists as-is(instead of changing it to NoSuchLedgerExistsOnDataServer) to minimize code changes. This change alone provides enough distinction between these two types of errors. Signed-off-by: Venkateswararao Jujjuri (JV) <vjujjuri@salesforce.com> * Checkstyle fixes * Some more fixes * Fixing DL test fixes
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.