commit | 10859afb7e8f2ee095e70f4e5482959bb5a3067a | [log] [tgz] |
---|---|---|
author | Matteo Merli <mmerli@apache.org> | Fri May 03 09:29:24 2019 -0700 |
committer | GitHub <noreply@github.com> | Fri May 03 09:29:24 2019 -0700 |
tree | 009ca1a6da3eed7d31beb7d6443ec2999168631e | |
parent | 707ae5c8536f967c0369f951d6178670c5dd031d [diff] |
Added HTTP handler to expose bookie state ### Motivation Allow to check the state of the bookie through HTTP. The main reason is to allow light-weight probes that can be run frequently to establish whether the bookie is running and meets a minimum readiness criteria. One example is to automatically wait until the bookie has completed the startup sequence. ### Changes Added new HTTP handler that exposes the values from the bookie `StateManager`. Reviewers: Ivan Kelly <ivank@apache.org>, Enrico Olivelli <eolivelli@gmail.com>, Jia Zhai <zhaijia@apache.org>, Sijie Guo <sijie@apache.org> This closes #1995 from merlimat/bookie-state
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.