commit | f8a5974a56cd18a613e16a181c76ab538b0e7ec5 | [log] [tgz] |
---|---|---|
author | Charan Reddy Guttapalem <cguttapalem@salesforce.com> | Tue Oct 29 06:34:06 2019 -0700 |
committer | Jia Zhai <zhaijia@apache.org> | Tue Oct 29 21:34:06 2019 +0800 |
tree | 90a3cdc91b390ea7ea1ca0049e9987758c7e510c | |
parent | 8559126a3ec00f2b1912d40d37b8bf8a000b0c4b [diff] |
Fix firstStoredEntryId logic in LedgerFragment Descriptions of the changes in this PR: - firstStoredEntryId logic in LedgerFragment should return '-1' only if no bookie contains any entry of that LedgerFragment. This is a serious issue, in our cluster we observed for a particular ledger, which is marked under replicated, it is returning -1 for firstStoredEntryId and 10 for lastStoredEntryId. Because of that the ReplicationWorker, tries to replicate entryId ‘-1’ and as expected it keeps failing while reading it. So ledger remains under replicated for ever. Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2180 from reddycharan/fixfirststoredentryidcom and squashes the following commits: 3cb8ae443 [Charan Reddy Guttapalem] change Long to long 9d9db66dd [Charan Reddy Guttapalem] minor log changes 37b025ccb [Charan Reddy Guttapalem] review comments 6e63fbb1e [Charan Reddy Guttapalem] review comments dbf836b32 [Charan Reddy Guttapalem] Fix firstStoredEntryId logic in LedgerFragment 2978a1a39 [Charan Reddy Guttapalem] Fix firstStoredEntryId logic in LedgerFragment
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.