commit | 42fe1506afe04b8068b897c530c7ca7188da503e | [log] [tgz] |
---|---|---|
author | Charan Reddy Guttapalem <reddycharan18@gmail.com> | Sat Jan 12 18:04:35 2019 -0800 |
committer | Sijie Guo <guosijie@gmail.com> | Sun Jan 13 11:04:35 2019 +0900 |
tree | 23dbe33f23ea68820b95b7747f71e32bb49603ec | |
parent | 4c8587715104cde6dbd70d1e7de0fc1853122eda [diff] |
Enhance EnsemblePlacementPolicy and DNSResolverDecorator to log relevant metrics. Descriptions of the changes in this PR: Make changes to EnsemblePlacementPolicy so that it would return boolean value indicating if the return value of newEnsemble and replaceBookie are strictly adhering to corresponding PlacementPolicy or it fell back to random. Similarly DNSResolverDecorator should log a metric when it was unable to resolve rack info and it is using default rack. Reviewers: Samuel Just <sjust@salesforce.com>, Sijie Guo <sijie@apache.org>, Venkateswararao Jujjuri (JV) <None> This closes #1883 from reddycharan/enhanceplacementpolicy
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.