commit | 63b3e5a0759f05fde752cc5ade07ea19a8f2b114 | [log] [tgz] |
---|---|---|
author | Jennifer Huang <47805623+Jennifer88huang@users.noreply.github.com> | Mon Dec 07 10:51:45 2020 +0800 |
committer | GitHub <noreply@github.com> | Sun Dec 06 18:51:45 2020 -0800 |
tree | 7454b4467326ea7ba0b1ecc9c115ebc2fe58dce7 | |
parent | 29b0a9ad3150a9de729d3586b374bc4ba17040b4 [diff] |
[DOCS] Update dbStorage_writeCacheMaxSizeMb configuration description Fixes #2500 ### Motivation The dbStorage_writeCacheMaxSizeMb configuration is not described clearly. ### Changes Refine the description in the broker.conf file. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None> This closes #2502 from Jennifer88huang/master and squashes the following commits: 505527085 [Jinfeng Huang] update 0de963832 [Jinfeng Huang] update dbStorage_writeCacheMaxSizeMb
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.