[ https://issues.apache.org/jira/browse/CASSANDRA-11966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Stupp updated CASSANDRA-11966: ------------------------------------- Resolution: Fixed Fix Version/s: 3.8 Status: Resolved (was: Patch Available) Looks good to me. +1 Committed as 7ede582fbd55dc959c3d3d26b4634b7472451e74 to trunk. Test results: ||trunk|[branch|https://github.com/apache/cassandra/compare/trunk...snazy:11966-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-11966-trunk-testall/lastSuccessfulBuild/]|[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-11966-trunk-dtest/lastSuccessfulBuild/] > 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 > Assignee: Chris Lohfink > Priority: Minor > Fix For: 3.8 > > Attachments: CASSANDRA-11966.patch, CASSANDRA-11966v3.patch > > > 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)