commit | 4d4465031012a126afcc78dcd3041829fee173d9 | [log] [tgz] |
---|---|---|
author | Enrico Olivelli <eolivelli@gmail.com> | Mon Nov 02 04:13:18 2020 +0100 |
committer | GitHub <noreply@github.com> | Mon Nov 02 11:13:18 2020 +0800 |
tree | cc408332a87a66d7a313afc10dc261fffb883a07 | |
parent | 417f0ea3a14c437a170042463d62d71e7db5e6a6 [diff] |
Issue 1533: DbLedgerStorage does not persist ExplicitLAC: Information (Header) of TransientLedgerInfo is not persisted (#2474) Motivation DbLedgerStorage does not persist "ExplicitLAC" on RocksDB, so when you restart a Bookie the information is lost. This work can be considered a follow up of @reddycharan work at #1527 Changes persist ExplicitLAC on DBLedgerStorage save ExplicitLAC on RocksDB (it is an optional field, so this change is backward compatible) enable testExplicitLACIsPersisted test even for DBLedgerStorage on TransientLedgerInfo rewind the ByteBuf in order to be able to use it again while writing to RocksDB use computeIfAbsent in getOrAddLedgerInfo (code clean up, but code looked strange, probably subject to some possible race condition) Master Issue: #1533 * Issue 1533: DbLedgerStorage does not persist ExplicitLAC: Information (Header) of TransientLedgerInfo is not persisted * final fix and fix checkstyle * restore tests Co-authored-by: Enrico Olivelli <eolivelli@apache.org>
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:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.
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.