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 (Commented) (JIRA)" <ji...@apache.org> on 2011/10/10 23:52:30 UTC

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

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

Flavio Junqueira commented on BOOKKEEPER-36:
--------------------------------------------

We might want to do it by bytes instead of number of requests. Also, throttling is currently done per ledger handle and not overall.
                
> 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
>            Priority: Critical
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira