commit | eb233b0e45623c9ff64387fde4428df57fff2344 | [log] [tgz] |
---|---|---|
author | Yong Zhang <zhangyong1025.zy@gmail.com> | Mon Jan 08 11:39:18 2024 +0800 |
committer | GitHub <noreply@github.com> | Mon Jan 08 11:39:18 2024 +0800 |
tree | 0e9a00227555ca2bb4da111a77d3de4a47ffaac8 | |
parent | 70e11c96f7a77035c4da4c01566c05b5f56bf9c6 [diff] |
Fix the autorecovery failed replicate by add entry fenced error (#4163) * Fix the autorecovery failed replicate by add entry fenced error --- ### Motivation #3783 changed the recovery add request flags. It causes when replication happening, if the ledger was fenced, the ledger can not be recovered. Because the recovery add flag is not added then the normal add is not allowed to a fenced ledger.
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