You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2021/05/07 00:56:58 UTC
[GitHub] [bookkeeper] greatle opened a new issue #2709: lost last entry?
greatle opened a new issue #2709:
URL: https://github.com/apache/bookkeeper/issues/2709
**QUESTION**
In test class：
https://github.com/apache/bookkeeper/blob/master/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/TestReadLastConfirmedAndEntry.java
testAdvancedLacWithEmptyResponse（）
A total of "expectedEntryIdToFail + 1" entries are written here, but only "expectedEntryIdToFail" entries are read
Where is the last entry and how to get it？
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [bookkeeper] greatle commented on issue #2709: lost last entry?
Posted by GitBox <gi...@apache.org>.
greatle commented on issue #2709:
URL: https://github.com/apache/bookkeeper/issues/2709#issuecomment-833992189
In a real bookkeeper cluster, the same is . If writer is close, the last entry can be read. Otherwise, the last entry can't be read all the time, no matter how long wait or call the "force()" method of writer. In actual production environment, it is possible to write N entries in a period of time, but only N -1 entries can be read immediately. The N-th entry can be read only when it is written to other data next time or close writes. This should be a bug?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [bookkeeper] ArvinDevel commented on issue #2709: lost last entry?
Posted by GitBox <gi...@apache.org>.
ArvinDevel commented on issue #2709:
URL: https://github.com/apache/bookkeeper/issues/2709#issuecomment-847077525
This is not a bug. Original BK protocol only piggyback LAC when appending new entry, so when you write the last entry, the writer can only piggyback (lastEntryId - 1) as LAC to the server. The newest BK protocol support write LAC intermittently by setting `explicitLacInterval` parameter.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org