commit | a8eb2d64ef040983493e65ed2c55e3255e3ee3b4 | [log] [tgz] |
---|---|---|
author | Fretiq Labs <60456830+fretiq@users.noreply.github.com> | Tue May 19 00:58:44 2020 -0500 |
committer | GitHub <noreply@github.com> | Mon May 18 22:58:44 2020 -0700 |
tree | 15ee245740a064f328471784c0dcd0b149796f73 | |
parent | a7ca7cff615391d1267f3546735e18b3306eb1e4 [diff] |
Add /api/v1/bookie/info REST API Descriptions of the changes in this PR: This adds an additional HTTP REST endpoint to expose the bookie's info (only storage numbers for now). ### Motivation I was looking for an HTTP endpoint that returned the info of only the current bookie, but couldn't find one. The only similar API I've found was `/api/v1/bookie/list_bookie_info`, however it connects to all bookies and may take a long time to respond (plus its response format is difficult to parse). ### Changes I've added a new API at `/api/v1/bookie/info` that returns a response like: ```json { "freeSpace" : 0, "totalSpace" : 0 } ``` Reviewers: Matteo Minardi <minardi.matteo@hotmail.it>, Enrico Olivelli <eolivelli@gmail.com>, Jia Zhai <zhaijia@apache.org> This closes #2322 from fretiq/add-bookie-info-api
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.