T Jake Luciani created CASSANDRA-10031:
------------------------------------------
Summary: Name threads for improved ops/debugging
Key: CASSANDRA-10031
URL: https://issues.apache.org/jira/browse/CASSANDRA-10031
Project: Cassandra
Issue Type: Improvement
Reporter: T Jake Luciani
Priority: Minor
Fix For: 3.x
We currently provide basic names for threads in threads like {{STREAM-IN-1}}
which gives some basic information about what the job of the thread is.
When looking at a log statement or jstack it's helpful to have this context.
For our work stealing thread pool we share threads across all thread pools so
we lose this insight.
I'd like to propose we start using the Thread.currentThread().setName("")
In different aspects of the code to improve insight as to what cassandra is
doing at any given moment.
* At a minimum in the start of each run() method.
Ideally for much finer grain things.
* In compaction include the partition name currently being working on.
* In SP include the client ip
Etc...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
