commit | f1df81f6590e048b93ec21776f931a28f0468a45 | [log] [tgz] |
---|---|---|
author | Sijie Guo <guosijie@gmail.com> | Mon Aug 26 11:15:15 2019 -0700 |
committer | GitHub <noreply@github.com> | Mon Aug 26 11:15:15 2019 -0700 |
tree | c099a5dab5ff983263faca6a0e39cda4ed777e44 | |
parent | 9e34c9a7e75b87441c2455139a715e39ff985f43 [diff] |
Journal should respect to `flushWhenQueueEmpty` setting Descriptions of the changes in this PR: *Motivation* Currently journal doesn't respect to `flushWhenQueueEmpty` setting. Even `flushWhenQueueEmpty` is set to false, we can still see flushes triggered due to queue empty. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Jia Zhai <zhaijia@apache.org> This closes #2147 from sijie/fix_flush_when_empty
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.