commit | a0d49fcb65a40b2b49fbfb6c50f60c7a9f66f67f | [log] [tgz] |
---|---|---|
author | Matteo Merli <mmerli@apache.org> | Wed Aug 26 16:46:28 2020 -0700 |
committer | GitHub <noreply@github.com> | Thu Aug 27 07:46:28 2020 +0800 |
tree | 8fe479ffb5c5f34a60ae3da2e5b6610d5ae75f35 | |
parent | af13a89c9cc3a90e0da361c9488a1cceb19506f8 [diff] |
Trigger flush if write cache is full while waiting (#2402) Under heavy load, the write cache can fill up faster than it can be flushed. When this occurs, something needs to trigger the flush. Previously we've triggered the flush and then gone into a loop waiting to be able to add to the write cache. However, if the currently active write cache fills while we are waiting for the flushing write cache to be flushed, we can end up in a situation where nothing is able to flush because all I/O threads are waiting for the write cache to empty. The solution is to move the flush into the loop so that if we fail to add to the cache, we flush the write cache if it is needed. Co-authored-by: Ivan Kelly <ikelly@splunk.com>
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.