commit | 52d195700381bb3782a86e983f1a8c62d12bad2a | [log] [tgz] |
---|---|---|
author | Ivan Kelly <ivank@apache.org> | Sat Dec 22 00:41:22 2018 +0100 |
committer | Sijie Guo <guosijie@gmail.com> | Sat Dec 22 07:41:22 2018 +0800 |
tree | ddd7f38087ad30b2860460df7eb66e7be9a4f999 | |
parent | 21d71fb9e576d95e2ff2adf7a961a2847b96a9f9 [diff] |
Multiple calls to LedgerHandle#close should wait on actual close The previous behaviour was to complete successfully immediately if close had already been called on the handle. This allowed for potential consistency violations, as the caller could believe that the ledger was closed, when in fact the close operation was still in progress and could still potentially fail. Issue: #1712 Reviewers: Sijie Guo <sijie@apache.org> This closes #1889 from ivankelly/double-close-anomoly
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.