[
https://issues.apache.org/jira/browse/CASSANDRA-12758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553766#comment-15553766
]
Michael Shuler commented on CASSANDRA-12758:
--------------------------------------------
I updated fixver to 2.2.x, 3.0.x, 3.x, 4.x. The 2.1 branch is critical-fix
only, so while I understand this is related, an improvement shouldn't be pushed
to 2.1. If some devs feel differently, I won't argue, however.
> Expose tasks queue length via JMX
> ---------------------------------
>
> Key: CASSANDRA-12758
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12758
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Romain Hardouin
> Priority: Minor
> Fix For: 2.2.x, 3.0.x, 3.x, 4.x
>
> Attachments: 0001-Add-MBean-to-monitor-max-queued-tasks_2.1.patch,
> 0001-Add-MBean-to-monitor-max-queued-tasks_trunk.patch
>
>
> CASSANDRA-11363 introduced {{cassandra.max_queued_native_transport_requests}}
> to set the NTR queue length.
> Currently Cassandra lacks of a JMX Mbean which exposes this value which would
> allow to:
>
> 1. Be sure this value has been set
> 2. Plot this value in a monitoring application to make correlations with
> other graphs when we make changes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
