[jira] [Closed] (STORM-271) Naming storm threads more meaningful names.

["Rick Kellogg (JIRA)" <ji...@apache.org>]

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

Rick Kellogg closed STORM-271.
------------------------------
    Resolution: Duplicate

> Naming storm threads more meaningful names.
> -------------------------------------------
>
>                 Key: STORM-271
>                 URL: https://issues.apache.org/jira/browse/STORM-271
>             Project: Apache Storm
>          Issue Type: Sub-task
>          Components: storm-core
>    Affects Versions: 0.9.2-incubating
>            Reporter: Sean Zhong
>            Priority: Minor
>              Labels: Debug, Performance
>
> In my test topology, each worker has 108 threads. Some  threads are generated from a thread pool with a vague name.
> For example, the netty threads, the worker receiver thread, the worker transfer threads, the disruptor thread are not good named.
> May be we should name them with a more meaningful name so that it is more easy for us to track the performance issues.
> Here is the naming I used:
> name            description
> -------------------------------------
> worker-transfer-thread: the single transfer thread for each worker
> worker-receiver-thread: the receiver thread for each worker
> netty-server-boss-host-port-seqenceId: the netty server boss thread.
> netty-server-worker-host-port-sequenceId:the netty server worker thread
> executor-disruptor-transfer-thread-[executorId]: executor transfer thread for disrupotor queue.
> netty-client-boss-targetHost-port-sequenceId: the netty client bos thread
> netty-client-worker-targetHost-port-sequenceId: the netty client worker thread.



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