commit | 0988e12c7a12e1ffae2cdbe932ba414ec06f40cc | [log] [tgz] |
---|---|---|
author | bd2019us <47727869+bd2019us@users.noreply.github.com> | Tue Apr 02 13:35:23 2019 -0500 |
committer | Sijie Guo <guosijie@gmail.com> | Tue Apr 02 11:35:23 2019 -0700 |
tree | f0d4f12b0e128b253f4b9b5eb79ee152fdf4392a | |
parent | 6a6d7bbd995acd55389ec209e42e099647c988fd [diff] |
ISSUE #2023: change cached thread pool to fixed thread pool Descriptions of the changes in this PR: change newCachedThreadPool() to newFixedThreadPool(int) ### Motivation newFixedThreadPool(int) can be freely configured with the total number of threads, while cached thread pool may cause OutOfMemoryError when there are too many threads need to created. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2024 from bd2019us/patch, closes #2023
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.