commit | bab5a003e84601469485cbcee4fc784171a1513d | [log] [tgz] |
---|---|---|
author | Andrey Yegorov <dlg99@users.noreply.github.com> | Thu Jan 28 00:12:05 2021 -0800 |
committer | GitHub <noreply@github.com> | Thu Jan 28 09:12:05 2021 +0100 |
tree | b89c0d5a6730a9b1c965ab9dfb893d0b13d992bf | |
parent | 6c3c9f7cf4bd4d6db5fcd4aee657c3a0f30fd2f4 [diff] |
Fixed: DLCheckpointStore rethrows exceptions as FNFE but swallows the rootcause DLCheckpointStore rethrows exceptions as FNFE but swallows the rootcause Same as https://github.com/apache/bookkeeper/pull/2553 but for master branch Descriptions of the changes in this PR: added .initCause for the new FNFE exception to preserver it ### Motivation got the ERROR org.apache.bookkeeper.statelib.impl.rocksdb.checkpoint.RocksCheckpointer - Failed to restore rocksdb ... java.io.FileNotFoundException: ..../metadata without any additional info for the rootcause (other than stack pointing to the DLCheckpointStore) DLCheckpointStore appears to re-throw exceptions as FNFE without preserving the rootcause ### Changes added .initCause Master Issue: #2552 Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2555 from dlg99/master-fnfe
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.