[
https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969481#comment-14969481
]
Venkateswararao Jujjuri commented on BOOKKEEPER-874:
----------------------------------------------------
Finally I started working on it.
I see that ReadLastAddConfirmedOp overloads readopertion with entryId set to -1
(LAST_ADD_CONFIRMED) indicating to the bookie what to do.
Similarly is it best to do AddLastAddConfirmedOp overloading addEntry()
operation? Here how should we indicate our intention to bookies? Add a new
flag, FLAG_LAC_ADD just like FLAG_RECOVERY_ADD?
Thanks,
JV
> 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)
