commit | c5e4c8645bb08c4b0ba65d15c8b4d0084bd09c68 | [log] [tgz] |
---|---|---|
author | Andrey Yegorov <8622884+dlg99@users.noreply.github.com> | Mon Feb 01 01:52:06 2021 -0800 |
committer | GitHub <noreply@github.com> | Mon Feb 01 10:52:06 2021 +0100 |
tree | 33fbfe95fe4a67db1f4fad64b03c6b2645e0ae59 | |
parent | 86ea505b6d0ab51432c2820d7517f78b61c44ae4 [diff] |
Handling checkpoint corruption in case of bookie crash Descriptions of the changes in this PR: Allowed fallback to previous checkpoint, assuming that corrupt checkpoint means that checkpointing did not complete and the journal is intact. ### Motivation Reliability and resilience of teh table service. ### Changes Allowed fallback to previous checkpoint, assuming that corrupt checkpoint means that checkpointing did not complete and the journal is intact. Master Issue: #2565 Reviewers: Surinder Singh, Enrico Olivelli <eolivelli@gmail.com> This closes #2566 from dlg99/master-checkpoint-corruption
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 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.