Github user sijie commented on the issue:
https://github.com/apache/bookkeeper/pull/180
you still need to call "readLastAddConfirmed". This change is not "long
poll", it is "piggy-back lac". It is an optimization on reducing the times of
calling readLastAddConfirmed. In a tailing case, most of the time you should
call getLastAddConfirmed, you keep reading until your current read entry is
moving beyond the value that #getLastAddConfirmed, which means you caught up
with the writer then you switch to call #readLastAddConfirmed. since lac is
piggy-back, so the value returned by #readLastConfirmed is advancing, hence you
don't need to call #readLastAddConfirmed that often.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
