commit | 1ddeb9bfd4ad5a016e76254391fb88c53f566f63 | [log] [tgz] |
---|---|---|
author | Surinder Singh <sursingh@gmail.com> | Tue Feb 02 01:21:54 2021 -0800 |
committer | GitHub <noreply@github.com> | Tue Feb 02 10:21:54 2021 +0100 |
tree | ffe342d45cc815759990347aca2ec2f38fc3deb6 | |
parent | dc235fe75cb19e3077140927a6702dc934124738 [diff] |
ISSUE #2567: Save last revision in rocksdb Descriptions of the changes in this PR: Save latest revision in rocksdb. ### Motivation Currently while restoring the complete transaction log is replayed. As the transaction log builds up over time, it takes longer and longer to restore the storage containers on a new pod. ### Changes Instead we will save the revision in the rocksdb. We will use the revision retrieved after restoring the last checkpoint to skip ahead in the journal logs and only replay the entries that are not included in the checkpoint Master Issue: #2567 Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Andrey Yegorov <andrea.yegorov@datastax.com>, Matteo Merli <mmerli@apache.org> This closes #2568 from sursingh/save-last-version, closes #2567
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.