LedgerHandle.readLastConfirmed does not work
--------------------------------------------
Key: BOOKKEEPER-162
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-162
Project: Bookkeeper
Issue Type: Bug
Components: bookkeeper-client
Affects Versions: 4.0.0
Reporter: Philipp Sushkin
Priority: Critical
Two bookkeeper clients.
1st continuously writing to ledger X.
2nd (bk.openLedgerNoRecovery) polling ledger X for new entries and reading them.
In response we always reveiceing 0 as last confirmed entry id (in fact we are
receiving -1 from each bookie RecoveryData but then in ReadLastConfirmedOp, but
uninitialized "long maxAddConfirmed;" takes priority in Math.max(...).
Main question - is given scenario is expected to work at all?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
