You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jim Witschey (JIRA)" <ji...@apache.org> on 2015/09/15 23:17:47 UTC

[jira] [Commented] (CASSANDRA-10044) Native-Transport-Requests is missing from the nodetool tpstats output in Cassandra 2.1

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

Jim Witschey commented on CASSANDRA-10044:
------------------------------------------

Thanks for the report and the patch; I've made a note on CASSANDRA-10018 to see if these can all be dealt with together.

> Native-Transport-Requests is missing from the nodetool tpstats output in Cassandra 2.1
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10044
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10044
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Wei Deng
>            Priority: Minor
>              Labels: patch
>         Attachments: 0001-Add-the-missing-Native-Transport-Requests-in-tpstats.patch
>
>
> It appears that in Cassandra 2.1 the output of "nodetool tpstats" has changed a bit, and Native-Transport-Requests is removed. This is a useful piece of statistics information to understand the pressure at the coordinator. Even though people can still use JMX or metrics reporter to get the same information, it is not as convenient as before (in Cassandra 2.0 this is exposed through tpstats).
> Looking at the code https://github.com/apache/cassandra/blob/cassandra-2.1/src/java/org/apache/cassandra/tools/NodeProbe.java#L1369-L1371, this appears to be caused by some restructure in the JMX metrics, and can be easily patched by adding "org.apache.cassandra.transport:type=*" into the list of thread pools we print out.
> I understand Sam filed another JIRA https://issues.apache.org/jira/browse/CASSANDRA-10018 just a few days ago. However, that is for versions 2.2 and beyond. The patch here is to specifically address a missing information in Cassandra 2.1.



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