commit | 44ee320b64ee1d47ee8b278a843bd033660b7aa0 | [log] [tgz] |
---|---|---|
author | Ivan Kelly <ivank@apache.org> | Fri Apr 19 02:40:07 2019 +0200 |
committer | Sijie Guo <guosijie@gmail.com> | Fri Apr 19 08:40:07 2019 +0800 |
tree | 11fe8d5a9040db446af988505fc3122b8449fca4 | |
parent | 316b71923e841c9fdb61159067c4bcf6075d1f21 [diff] |
k Otherwise the watch objects will accumulate and eventually cause an OOM on the bookie, if LAC doesn't progress. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Matteo Merli <mmerli@apache.org>, Venkateswararao Jujjuri (JV) <None> This closes #2051 from ivankelly/tme-oom
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.