| commit | b88f4b813f5ee5846b4879972e2c8359ac0eb4f2 | [log] [tgz] |
|---|---|---|
| author | Ankit Jain <ankit.mcs@gmail.com> | Fri May 31 17:24:55 2019 -0700 |
| committer | Charan Reddy Guttapalem <reddycharan18@gmail.com> | Fri May 31 17:24:55 2019 -0700 |
| tree | 878c6b5311400590fa92f84b9629154390298dac | |
| parent | f89e3fbb751fbef7012e695ed5873eade13ba4f5 [diff] |
Entries must be acknowledged by bookies in multiple fault domains before being acknowledged to client Descriptions of the changes in this PR: Bookkeeper write logic makes sure that there are at least ackQuorumSize number of successful writes before sending ack back to the client. In many cases these may fall into the same fault domain. A mechanism to force bookkeeper to make sure that there are acks from at least minNumRacksPerWriteQuorum number of fault domains and a configuration to enforce this. Signed-off-by: Ankit Jain <jain.asalesforce.com> Master Issue: #2095 Reviewers: Charan Reddy Guttapalem <reddycharan18@gmail.com>, Enrico Olivelli <eolivelli@gmail.com> This closes #2096 from ankit-j/ankit-j/enforceFragmentMultipleFaultDomainWrite and squashes the following commits: c90fd5a3d [Ankit Jain] Addressing review comments 07deae673 [Ankit Jain] Addressing @reddycharan's review comments 14164e291 [Ankit Jain] Fixed spacing error in bk_server.yaml 22c8b3c03 [Ankit Jain] Updated testing. 917ed1c45 [Ankit Jain] Move readLock.unlock to finally block 78e0cd501 [Ankit Jain] Modify test to not use default rack for bookies ca0bc3b8b [Ankit Jain] Entries must be acknowledged by bookies in multiple fault domains before being acknowledged to client d35aa22ad [Charan Reddy Guttapalem] Move common placementpolicy components to TopologyAwareEnsemblePlacementPolicy.
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.