commit | 15a38405bcd527cfcdd926ad356d0ea682a9a9be | [log] [tgz] |
---|---|---|
author | Lari Hotari <lhotari@users.noreply.github.com> | Mon Apr 08 01:24:16 2024 -0700 |
committer | GitHub <noreply@github.com> | Mon Apr 08 16:24:16 2024 +0800 |
tree | 779e9f3ee98d170c4a95f799a1e307d5617a1bd4 | |
parent | 8ca4118d51989ad301bdc517c7552f05e6fdd4ee [diff] |
Use vertx blockingHandlers that allow blocking without warnings (#4266) ### Motivation - The http handler implementations in Bookkeeper aren't necessarily non-blocking. That's why they should be executed on the blocking thread pool in vertx. ### Changes Executing on blocking thread pool in vertx can be achieved by registering the handlers using the `blockingHandler` method instead of the `handler` method.
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:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a GitHub issue.
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 our installation guide to get your local environment setup.
Take a look at our open issues: GitHub Issues.
Review our coding style and follow our pull requests to learn more about our conventions.
Make your changes according to our contributing guide