tree 90a3cdc91b390ea7ea1ca0049e9987758c7e510c
parent 8559126a3ec00f2b1912d40d37b8bf8a000b0c4b
author Charan Reddy Guttapalem <cguttapalem@salesforce.com> 1572356046 -0700
committer Jia Zhai <zhaijia@apache.org> 1572356046 +0800

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