You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2017/06/02 20:18:04 UTC

[jira] [Created] (BOOKKEEPER-1093) Piggyback LAC on ReadResponse

Sijie Guo created BOOKKEEPER-1093:
-------------------------------------

             Summary: 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.3.15#6346)