[
https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749189#comment-15749189
]
ASF GitHub Bot commented on BOOKKEEPER-874:
-------------------------------------------
Github user sijie commented on the issue:
https://github.com/apache/bookkeeper/pull/89
@jvrao
isn't the lac buffer also just cached?
I am fine with the lac buffer (although that is not perfect, as I mentioned
above).
i think the middle ground for this patch here is :
piggyback lac and explicit lac should be just two ways to advance lac. we
should treat them as same for advancing lac in bookie.
- when an entry is added, it should advance the lac in FileInfo and trigger
listeners about lac is advanced
- when an explicit lac flush happened, it should do the same thing.
does that work for you?
> 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 (JV)
> Assignee: Venkateswararao Jujjuri (JV)
>
> 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)
