commit | 98df593ba432eb08b18d98331201099cc72879dc | [log] [tgz] |
---|---|---|
author | Yong Zhang <zhangyong1025.zy@gmail.com> | Mon Mar 08 19:04:18 2021 +0800 |
committer | GitHub <noreply@github.com> | Mon Mar 08 12:04:18 2021 +0100 |
tree | 018d04ae41da966398dd79159707f0f007a7eb26 | |
parent | 346e375f80322e5f328eafd4cb4040f177b6973b [diff] |
Allow force compact entry log when disabling entry log compaction --- Master Issue: #2596 *Motivation* Sometimes user will disable the entry log compaction to reduce the I/O load. But we should allow forcing compact the entry even if the entry log compaction is disabled. *Modifications* - Add a configuration to allow force compaction Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Jia Zhai <zhaijia@apache.org>, lipenghui <penghui@apache.org> This closes #2626 from zymap/allow-force-gc-without-interval
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:
Please visit the Documentation from the project website for more information.
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.