commit | 76eea92dcbc46e05aa20360d64ebf6fa169ea2b8 | [log] [tgz] |
---|---|---|
author | yapeng <562250082@qq.com> | Wed Aug 24 08:25:58 2022 +0800 |
committer | Yong Zhang <yong@apache.org> | Wed Aug 24 00:42:51 2022 +0000 |
tree | 1859ca00fcfdf94411780a8742a5110928633ece | |
parent | 7dfd51d3742389ed8e296e16ab58e4c276d73c1f [diff] |
move forceWriteMarkerSent out of loop of ForceWriteThread to avoid frequently forceWrite (#3454) Fix group ForceWrite not take effect with forceWriteMarkerSent in while loop of ForceWriteThread ### Motivation Bookkeeper 4.15 has performance issue. There are too many journal sync. Then I found in ForceWriteThread, forceWriteMarkerSent is reset to false for every loop, and this can cause shouldForceWrite=true and trigger journal sync. This new logic is bringed by https://github.com/apache/bookkeeper/pull/2962 ### Changes move forceWriteMarkerSent=false out of while loop. (cherry picked from commit dcc9a414eafbb27ed8d9a976ef824e825777273a)
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.
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 our installation guide to get your local environment setup.
Take a look at our open issues: Github Issues.
Review our coding style and follow our pull requests to learn more about our conventions.
Make your changes according to our contributing guide