[
https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979063#comment-14979063
]
Venkateswararao Jujjuri commented on BOOKKEEPER-874:
----------------------------------------------------
Looks like we need to change Readside too; As readside just returns last entry
instead of returning just LAC.
This may not be very good for the network too if that entry happens to be big
and also if ensemble + quorum sizes also big.
With this change there is going to be LAC along with entry, as it is today, and
also there is another LAC in FileInfo.
So the new GET_LAC need to read lastEntry, extract entryId from it, also read
from FIleInfo and return the highest of the two.
so now looks like we need to add two more operations to the protocol?
PUT_LAC GET_LAC
> 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)
