You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2013/07/07 02:59:48 UTC

[jira] [Updated] (BOOKKEEPER-602) we should have request timeouts rather than channel timeout in PerChannelBookieClient

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

Sijie Guo updated BOOKKEEPER-602:
---------------------------------

    Attachment: BOOKKEEPER-602.diff

attach a patch having request timeout rather than channel timeout.
                
> we should have request timeouts rather than channel timeout in PerChannelBookieClient
> -------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-602
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-602
>             Project: Bookkeeper
>          Issue Type: Bug
>    Affects Versions: 4.2.0, 4.2.1
>            Reporter: Sijie Guo
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-602.diff
>
>
> currently we only have readTimeout in netty channel, it timeouts only when there is no activities in that channel, but it can't track timeouts of individual requests. if a channel continues having read entry activities, it might shadow a slow add entry response, which is bad impacting add latency.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira