[
https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904675#comment-14904675
]
Flavio Junqueira commented on BOOKKEEPER-874:
---------------------------------------------
bq. Can't we update LAC of the last entry in place on bookies? Does this
violate any BookKeeper's principles?
My concern here is that it breaks the flow of the write pipeline. but other
than that, I don't see a correctness issue.
bq. alternatively reader may try to read ack quorum reads for LAC+1
yeah, that isn't really safe.
> 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)
