Sijie, > it is non-trivial to do that right now. because bookies don't store LAC out side of entries. > to support this, we might need to ledger storage to store LAC somewhere.
Can't we update LAC of the last entry in place on bookies? Does this violate any BookKeeper's principles? Thanks, JV On Wed, Sep 23, 2015 at 6:35 AM, Venkateswararao Jujjuri (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904510#comment-14904510 > ] > > Venkateswararao Jujjuri commented on BOOKKEEPER-874: > ---------------------------------------------------- > > alternatively reader may try to read ack quorum reads for LAC+1. This is > not elegant but with client change it is contained within. > > > > > -- > Sent from iPhone > > > > 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) > -- Jvrao --- First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi
