commit | 26e8004e6b93f5acaff7f69dba14511a7cf44d58 | [log] [tgz] |
---|---|---|
author | Charan Reddy Guttapalem <cguttapalem@salesforce.com> | Sun May 19 19:53:36 2019 -0700 |
committer | Sijie Guo <guosijie@gmail.com> | Mon May 20 10:53:36 2019 +0800 |
tree | 7b5e8fe64e4345f91b04468f3fcdc7ad1963cf39 | |
parent | dba831375ad0f10821c04258fb08f70cce3f4b67 [diff] |
Fix flaky testIOVertexHTTPServerEndpointForARWithPrometheusProvider test Descriptions of the changes in this PR: - in testIOVertexHTTPServerEndpointForARWithPrometheusProvider test it is not correct to assume that Auditor would have been created and started completely when we complete AutoRecoveryMain.start and see it status as started. It would make sure AuditorElector.submitElectionTask has submitted election task but not the completion of Auditor.start. So instead of relying on Auditor metric (NUM_UNDER_REPLICATED_LEDGERS), use ReplicationWorker metric - NUM_FULL_OR_PARTIAL_LEDGERS_REPLICATED. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2093 from reddycharan/fixflakytest
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.