commit | 0f22d238c225ec667c58e1c5029644478d636128 | [log] [tgz] |
---|---|---|
author | Andrey Yegorov <8622884+dlg99@users.noreply.github.com> | Mon May 03 11:44:55 2021 -0700 |
committer | GitHub <noreply@github.com> | Mon May 03 11:44:55 2021 -0700 |
tree | 9bf496929489a8f913b19d9dc1500373718afd50 | |
parent | e5e76667b0801fee42ccd0fe201fe72ce500a70d [diff] |
fix: Bookkeeper client throttling logic is based upon entryId instead of ledgerId Descriptions of the changes in this PR: Fixes: #2660 ### Changes isWriteSetWritable() to use ledgerId for the client selection Master Issue: #2660 Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Ivan Kelly <ivank@apache.org> This closes #2664 from dlg99/fix/2660
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.