[
https://issues.apache.org/jira/browse/BOOKKEEPER-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059383#comment-16059383
]
Hudson commented on BOOKKEEPER-1093:
------------------------------------
FAILURE: Integrated in Jenkins build bookkeeper-master #1792 (See
[https://builds.apache.org/job/bookkeeper-master/1792/])
BOOKKEEPER-1093: Piggyback LAC on ReadResponse (sijie: rev
90e4e46bccdd1a788e10056f4a3818aa2aead452)
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/PerChannelBookieClient.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerRecoveryOp.java
* (edit)
bookkeeper-server/src/test/java/org/apache/bookkeeper/test/BookieClientTest.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/conf/ClientConfiguration.java
* (edit)
bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingReadOp.java
* (add)
bookkeeper-server/src/test/java/org/apache/bookkeeper/client/TestPiggybackLAC.java
> Piggyback LAC on ReadResponse
> -----------------------------
>
> Key: BOOKKEEPER-1093
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1093
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.5.0
>
>
> Currently LAC is only updated when the reader explicitly calls
> #readLastAddConfirmed(). In tailing-read use cases, it will not wise to keep
> calling #readLastAddConfirmed, especially when the traffic is huge.
> The idea here is piggy-back LAC along with the read responses. so the client
> will get advanced LAC along with read responses. so it will reduce calling
> #readLastAddConfirmed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
