commit | 9540d8473ebbe49425ece1088047cd544e8427f9 | [log] [tgz] |
---|---|---|
author | Charan Reddy Guttapalem <reddycharan18@gmail.com> | Tue Aug 13 10:53:39 2019 -0700 |
committer | GitHub <noreply@github.com> | Tue Aug 13 10:53:39 2019 -0700 |
tree | ca4a9551e9722bccdaedf3e7b9dfbe3698eb88f7 | |
parent | 0034fe684136e318d1a7e8b384968d703d2dd8c4 [diff] |
Replicascheck comprehensive testcases. Descriptions of the changes in this PR: - adding comprehensive testcases for newly added scrutiny - replicasCheck. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None> This closes #2141 from reddycharan/replicaschecktest
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.