[
https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904759#comment-14904759
]
Flavio Junqueira commented on BOOKKEEPER-874:
---------------------------------------------
bq. Are you worried about the case where reader may read ahead of writer got
Acks and crashes before returning to the user? I agree this solution does have
that corner case issue.
Yes, in general that's the problem of reading ahead of the LAC.
bq. In theory yes. But this happens only when writes are sparse i.e if there is
a write pipeline we won't even come to this case right?
The write pipeline interleaves adds from all ledgers being written to
concurrently, so it isn't only for that one ledger you're updating. But, if the
bookie is mostly idle, then it is definitely not a problem.
> 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)
