commit | 637bfa756ddba08bf5f67fc2d45124afd5dbc0bc | [log] [tgz] |
---|---|---|
author | Matteo Minardi <minardi.matteo@hotmail.it> | Wed May 27 08:14:01 2020 +0200 |
committer | GitHub <noreply@github.com> | Wed May 27 08:14:01 2020 +0200 |
tree | c1c5f7c0531e19b8b26ab2b9f17afc4729e2948f | |
parent | f15b9bd15766d87d04258387a1164260056e088b [diff] |
BP-38: Publish Bookie Service Info on Metadata Service Starting from the implementation of the #2213 PR ### Changes - Adding the ability for the Bookie to advertise on the Metadata Service (ZooKeeper) the exposed ports/services, like the HTTP service, Metrics - Implemented the Protobuf serialization of the BookieServiceInfo - Added the command EndpointInfoCommand to retrieve remote bookie endpoint information both for "bkctl" and "bookkeeper shell". Usage: ` bin/bookkeeper shell endpointinfo -bookieid <bookieaddress> ` Master Issue: #2215 Proposal Doc: https://bookkeeper.apache.org/bps/BP-38-bookie-endpoint-discovery Reviewers: Jia Zhai <zhaijia@apache.org>, Enrico Olivelli <eolivelli@gmail.com> This closes #2314 from mino181295/single/endpoint-discovery-impl
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.