[jira] [Updated] (CASSANDRA-10031) Name threads for improved ops/debugging

2019-06-13 Thread Jeremy Hanna (JIRA)


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

Jeremy Hanna updated CASSANDRA-10031:
-
Complexity: Low Hanging Fruit

> Name threads for improved ops/debugging
> ---
>
> Key: CASSANDRA-10031
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10031
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Legacy/Observability
>Reporter: T Jake Luciani
>Priority: Low
>  Labels: lhf
> Fix For: 4.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
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-10031) Name threads for improved ops/debugging

2018-11-18 Thread C. Scott Andreas (JIRA)


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

C. Scott Andreas updated CASSANDRA-10031:
-
Component/s: Observability

> Name threads for improved ops/debugging
> ---
>
> Key: CASSANDRA-10031
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10031
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Observability
>Reporter: T Jake Luciani
>Priority: Minor
>  Labels: lhf
> Fix For: 4.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
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-10031) Name threads for improved ops/debugging

2015-09-22 Thread T Jake Luciani (JIRA)

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

T Jake Luciani updated CASSANDRA-10031:
---
Labels: lhf  (was: )

> 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
>  Labels: lhf
> 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)