commit | b4ca4537b62e75f71e3329186652f982025175a2 | [log] [tgz] |
---|---|---|
author | Charan Reddy Guttapalem <reddycharan18@gmail.com> | Fri May 10 09:59:17 2019 -0700 |
committer | GitHub <noreply@github.com> | Fri May 10 09:59:17 2019 -0700 |
tree | 51a128cca550d2c4f562e620a2f619c98f341ee2 | |
parent | aa84c7fdd24a925f57f087670b205a35fb8ef237 [diff] |
Move common placementpolicy components to TopologyAwareEnsemblePlacementPolicy. Descriptions of the changes in this PR: - Moving components/methods which are common in nature with respect to placementpolicy from RackawareEnsemblePlacementPolicyImpl to TopologyAwareEnsemblePlacementPolicy, so that any new placementpolicy implementation can extend TopologyAwareEnsemblePlacementPolicy and reuse those common components/generic. - This change has no functionality change, it is just reorganizing code. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2089 from reddycharan/3azplacement
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.