[jira] [Comment Edited] (BOOKKEEPER-874) Explict LAC from Writer to Bookies

["Flavio Junqueira (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904821#comment-14904821 ] 

Flavio Junqueira edited comment on BOOKKEEPER-874 at 9/23/15 5:01 PM:
----------------------------------------------------------------------

bq. an entry is digested with entryid, lac and entry data.

Indeed, good point.

bq. we could have lac in FileInfo and be durable like what we did for fencing state. so we don't need additional cache.

I don't see a problem with that, and making it durable sounds like a bonus.


was (Author: fpj):
bq. an entry is digested with entryid, lac and entry data.

Indeed, good point.

> 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)