commit | 29b0a9ad3150a9de729d3586b374bc4ba17040b4 | [log] [tgz] |
---|---|---|
author | Enrico Olivelli <eolivelli@gmail.com> | Mon Dec 07 03:50:36 2020 +0100 |
committer | GitHub <noreply@github.com> | Sun Dec 06 18:50:36 2020 -0800 |
tree | ce903bb5f71e37f2a0c4d21038fd565684b0c7e9 | |
parent | 5741f052d4fd17690a21d2ca5071fe190e0cdaa0 [diff] |
getBookieInfo is stuck if no bookie is up (#2498) ### Motivation getBookieInfo is stuck if no bookie is up ### Changes Fix the problem, add a test case. Also the getBookieInfoTimeout configuration was not used, we were using the read entry timeout.
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.