commit | 67208fb74181faa640e793cd5757712fd9b5d9d5 | [log] [tgz] |
---|---|---|
author | AloysZhang <lofterzhang@gmail.com> | Sun Jul 31 11:30:45 2022 +0800 |
committer | GitHub <noreply@github.com> | Sun Jul 31 11:30:45 2022 +0800 |
tree | a9530fb852f4d362f7df2ccdffe714acc8364485 | |
parent | 8c557f9f16bf150d2efd010b5f5939fe44aef740 [diff] |
issue #2879 : let bookie quit if journal thread exit (#2887) Descriptions of the changes in this PR: fix #2879 This pull request let bookie quit when there's journal thread exit ### Motivation As described in #2879, now if a bookie has multi journal directories means it has multi journal thread. Once a journal thread exits, the bookie will be unhealthy due to the block of all bookie-io threads, and then the bookie will not work but progress is still alive. This pull request tries to fix this problem. ### Changes check the journal thread alive in a fixed interval, let bookie quit once there's a journal thread exit
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