[jira] [Commented] (BOOKKEEPER-670) Longpoll Read & Piggyback Support

["Venkateswararao Jujjuri (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012251#comment-15012251 ] 

Venkateswararao Jujjuri commented on BOOKKEEPER-670:
----------------------------------------------------

Current writer piggy-backs LAC in the header and digest's it before sending to bookies, and if bookies need to interpret LAC and send it back, it needs to calculate and validate the digest before sending it back right? This may add huge performance penalty of course it adds additional validate that the packed did not get corrupted on the wire though. 
Is this the motto? or am I missing something?

> Longpoll Read & Piggyback Support
> ---------------------------------
>
>                 Key: BOOKKEEPER-670
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-670
>             Project: Bookkeeper
>          Issue Type: New Feature
>          Components: bookkeeper-client, bookkeeper-server
>            Reporter: Sijie Guo
>            Assignee: Robin Dhamankar
>             Fix For: 4.4.0
>
>         Attachments: LACNotificationonBookKeeper.pdf
>
>
> LastAddConfirmed (LAC) is a hint entry id carried on each entry written by a ledger writer, which indicates that all the entries before LAC have already acknowledged by the writer. So the reader is safe to read all the entries written before LAC.
> Currently a bookkeeper reader doesn’t sync LAC with the bookkeeper writer. So a bookkeeper reader has to read LAC (aka LedgerHandle#readLastConfirmed) before getting the latest entries written by the writer.
> Such polling behavior results in poor performance:
> * Delay on reading entries if we are setting a larger polling interval.
> ** ReadLastConfirm needs to wait all the responses from all bookies in last ensemble. This constraint is required for Ledger Recovery Procedure, but not for the reader just needs to know latest LAC.
> * It might Introduce useless polling loads to bookie servers if we are setting a smaller polling interval.
> A notification mechanism is good to reduce round-trips that a reader spent on polling LAC.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)