You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2017/10/06 08:39:00 UTC

[jira] [Updated] (BOOKKEEPER-36) Client backpressure

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-36:
---------------------------------
    Priority: Major  (was: Critical)

> Client backpressure
> -------------------
>
>                 Key: BOOKKEEPER-36
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-36
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-client
>            Reporter: Flavio Junqueira
>            Assignee: Flavio Junqueira
>              Labels: iktriage0
>
> The way we currently throttle on the client is by counting the number of outstanding operation on LedgerHandle, and having the application select what an appropriate value is. This is not a good way of doing it because the application has to guess what a good value is. We need to implement some form of backpressure instead to make sure we throttle only when the system is saturated. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)