[
https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979181#comment-14979181
]
Sijie Guo commented on BOOKKEEPER-874:
--------------------------------------
for read lac, in BOOKKEEPER-670, we are going to add LAC field in ReadResponse
to piggyback maximum lac and also provide a long poll mechanism for lac and
entry. that field could be leveraged for returning lac.
returning last entry is kind of necessary, since the entry needs to pass the
checksum (digestion) validation before claiming lac is validate. otherwise, it
potentially would return a corrupted LAC which cause correctness issue.
so:
- for the lac stored in file info, we need to checksum it too.
- for reading lac, I would suggest leveraging the protocol changes will be made
in BOOKKEEPER-670.
> Explict LAC from Writer to Bookies
> ----------------------------------
>
> Key: BOOKKEEPER-874
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-874
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-client, bookkeeper-server
> Reporter: Venkateswararao Jujjuri
> Assignee: Venkateswararao Jujjuri
>
> Current client API piggy-backs LAC with a write. This is keeps reader one
> behind the writer. In order to keep reader up to date with writer even when
> there is a pause in write, proposing the following:
> Writer sends explicit LAC on a configured timeout if there is no write within
> that period.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
