[
https://issues.apache.org/jira/browse/CASSANDRA-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975429#comment-16975429
]
Chris Lohfink commented on CASSANDRA-12197:
-------------------------------------------
It was actually idea behind CASSANDRA-8341 which could be exposed in the
thread_pools virtual table or tpstats. Its more efficient to hit the Thread
mbean locally than to make individual RMI calls on each thread at high rates
but to capture it cross stages gets complicated with SEP as its switches
between stages. This also is something that sjk makes a bit confusing as a
MutationStage thread can switch to a ReadStage from 1 query to another with
same threadid making it inaccurately report. Of course in practice it doesn't
matter and is incredibly valuable even with inaccuracies.
> Integrate top threads command in nodetool
> -----------------------------------------
>
> Key: CASSANDRA-12197
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12197
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: J.B. Langston
> Assignee: Ekaterina Dimitrova
> Priority: Low
>
> SJK (https://github.com/aragozin/jvm-tools) has a command called ttop that
> displays the top threads within the JVM, sorted either by CPU utilization or
> heap allocation rate. When diagnosing garbage collection or high cpu
> utilization, this is very helpful information. It would be great if users
> can get this directly with nodetool without having to download something
> else. SJK is Apache 2.0 licensed so it might be possible leverage its code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
