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

Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2016/06/07 17:05:21 UTC

[jira] [Commented] (CASSANDRA-11966) When SEPWorker assigned work, set thread name to match pool

    [ https://issues.apache.org/jira/browse/CASSANDRA-11966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318890#comment-15318890 ] 

Robert Stupp commented on CASSANDRA-11966:
------------------------------------------

Yup - during runtime, it's a cheap operation. This is a nice improvement - mind providing a patch?
Just please add a system property to be able to turn this feature off - some profilers get crazy when you change thread names.

> When SEPWorker assigned work, set thread name to match pool
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-11966
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11966
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: Chris Lohfink
>            Priority: Minor
>
> Currently in traces, logs, and stacktraces you cant really associate the thread name with the pool since its just "SharedWorker-#". Calling setName around the task could improve logging and tracing a little while being a cheap operation.



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