commit | 114de135f402d2f8de045fb9413e804247841def | [log] [tgz] |
---|---|---|
author | Charan Reddy Guttapalem <cguttapalem@salesforce.com> | Fri Oct 11 08:22:54 2019 -0700 |
committer | Enrico Olivelli <eolivelli@gmail.com> | Fri Oct 11 17:22:54 2019 +0200 |
tree | 7bf9c67b19b4910555b1b9a38d8a264c8bda749f | |
parent | 14c9979047bb4ecd30619a9184e446c2e87fec26 [diff] |
Call exceptionHandler if Bookie.start fails with exception. Descriptions of the changes in this PR: When main thread of Bookie/BookieServer has exited with exception while starting Bookie, Bookie process shouldn't be alive because of any non-daemon thread that has already started. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Karan Mehta <k.mehta@salesforce.com> This closes #2173 from reddycharan/fixbookiestartup
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.