You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2015/09/22 23:42:04 UTC
[jira] [Commented] (BOOKKEEPER-874) Explict LAC from Writer to
Bookies
[ https://issues.apache.org/jira/browse/BOOKKEEPER-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903500#comment-14903500 ]
Flavio Junqueira commented on BOOKKEEPER-874:
---------------------------------------------
[~jujjuri] that's a good idea, for ledgers with low traffic, the reader sits there waiting to consume records unnecessarily.
> 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)