commit | efaa993a6c0bde9e2773dc598a4812a4b678de7a | [log] [tgz] |
---|---|---|
author | Surinder Singh <sursingh@gmail.com> | Fri Jan 29 12:03:29 2021 -0800 |
committer | GitHub <noreply@github.com> | Fri Jan 29 12:03:29 2021 -0800 |
tree | f89124ef15e96c4b5133126792031a5a322eec87 | |
parent | bab5a003e84601469485cbcee4fc784171a1513d [diff] |
ISSUE #2563: Fix SST file corruption. Fix SST File corruption during checkpointing ### Motivation Since the SST files are shared among checkpoints, this will not be resolved by future checkpoints. We will fail to restore all future checkpoints that depend on this file. ### Changes The record is sent asynchronously. We need to use a copy of the passed buffer in the record. The ownership is retained by the caller and will be potentially changed by the caller. In case of corruption the later blocks were overwriting the previous blocks resulting in corruption Master Issue: #2563 Reviewers: Andrey Yegorov <None>, Enrico Olivelli <eolivelli@gmail.com>, Matteo Merli <mmerli@apache.org> This closes #2564 from sursingh/fix-sst-corruption, closes #2563
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.