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

Posted to dev@bookkeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2014/03/03 19:38:32 UTC

[jira] [Reopened] (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 ]

Rakesh R reopened BOOKKEEPER-602:
---------------------------------


IMHO, it would be good to backport the changes to branch4.2 as well. Please feel free to close if anyone has different opinion. Thanks

> 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
>            Assignee: Aniruddha
>             Fix For: 4.3.0, 4.2.3
>
>         Attachments: 0001-BOOKKEEPER-602-we-should-have-request-timeouts-rathe.patch, BOOKKEEPER-602.diff, 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 was sent by Atlassian JIRA
(v6.2#6252)