commit | fe0e0d88b4f36e25aebd81c5b3596cbcd2c2d21e | [log] [tgz] |
---|---|---|
author | Arvin <arvindevel@gmail.com> | Tue Apr 02 00:27:42 2019 +0800 |
committer | Matteo Merli <mmerli@apache.org> | Fri May 03 09:52:38 2019 -0700 |
tree | cd76e161321e9895358a9ed9071103bf1dacee91 | |
parent | c89d6afd53ac98e0302002521d06699d4d710c3a [diff] |
ISSUE #2020: close db properly to avoid open RocksDB failure at the second time Descriptions of the changes in this PR: ### Motivation If not releasing resources of failed/closed asyncStore, new creating of the same store identifier will fail, mainly caused by RocksDBException, like #2020 shows. ### Changes add scStores to factory's instance variable at the `addstore` method of `MVCCStoreFactoryImpl` class; release store when open fail; Descriptions of the changes in this PR: Master Issue: #2020 Reviewers: Jia Zhai <zhaijia@apache.org>, Sijie Guo <sijie@apache.org> This closes #2022 from ArvinDevel/issue2020, closes #2020
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.