You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Roshan Naik (JIRA)" <ji...@apache.org> on 2017/07/19 22:28:00 UTC

[jira] [Created] (STORM-2647) Reduce Number of Threads running in the Worker

Roshan Naik created STORM-2647:
----------------------------------

             Summary: Reduce Number of Threads running in the Worker
                 Key: STORM-2647
                 URL: https://issues.apache.org/jira/browse/STORM-2647
             Project: Apache Storm
          Issue Type: Sub-task
            Reporter: Roshan Naik


Below is an account of all the threads in a single worker running a topology with 1 spout instance, 1 bolt instance, and 1 acker bolt instance. Topology debugging feature was disabled as it brings in additional threads.

Total 34 threads:  
10 timer threads
2 Curator threads
2 ZooKeeper threads
4 Netty threads
7 Disruptor thread
1 Spout executor thread
2 worker thread
1 Back Pressure thread
4 thread - unclear what these are
1 Finalizer thread



- Would be good to collapse the Timer threads into SingleThreadScheduledExecutor.
- We have 4 threads to communicate with ZK (2curator + 2ZK). If necessary can we eliminate curator to accomplish that ?
- Similarly see if we can reduce the number of Netty threads.
- How many threads does topology debugging need, can we reduce that ?
- The Back pressure and Disruptor threads will be reduced by STORM-2306 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)