You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/09 03:29:29 UTC

[jira] [Reopened] (STORM-272) Make worker receiver thread number configurable

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

Rick Kellogg reopened STORM-272:
--------------------------------

> Make worker receiver thread number configurable
> -----------------------------------------------
>
>                 Key: STORM-272
>                 URL: https://issues.apache.org/jira/browse/STORM-272
>             Project: Apache Storm
>          Issue Type: Sub-task
>    Affects Versions: 0.9.2-incubating
>            Reporter: Sean Zhong
>            Priority: Minor
>
> In my profiling, I found the receiver thread of worker can be a performance bottle-neck. 
> Now each worker has single receiver thread, and it is responsbile to transfer information generated from multiple netty client to tens of executor disruptor queue. It is too much for busy topology.
> Without this fix, we have to increase the number of workers, which will create more intra-worker traffic that we don't want. 
>  
> I suggest that we can add a config called "worker.receiver.thread.count" to control the parallism of the receiver thread, and make it default to 1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)