You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Utkarsh Srivastava (JIRA)" <ji...@apache.org> on 2011/08/11 07:57:27 UTC
[jira] [Commented] (BOOKKEEPER-44) Reuse publish channel to default
server to avoid too many connect requests to default server when lots of
producers came in same time
[ https://issues.apache.org/jira/browse/BOOKKEEPER-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082943#comment-13082943 ]
Utkarsh Srivastava commented on BOOKKEEPER-44:
----------------------------------------------
+1, LGTM
> Reuse publish channel to default server to avoid too many connect requests to default server when lots of producers came in same time
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-44
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-44
> Project: Bookkeeper
> Issue Type: Improvement
> Components: hedwig-client
> Affects Versions: 3.4.0
> Reporter: Sijie Guo
> Fix For: 3.4.0
>
> Attachments: bookkeeper-44.patch
>
>
> Currently when client wants to publish messages to a specific topic (client doesn't know which hub owns this topic), it needs to ask default server which hub owns it. Client needs to connect to default server each time, even the channel to default server has been established. So too many unused connections will be opened and closed, when it publishes to different topics concurrently.
> Reuses existed channel to default server to avoid the above issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira