You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2010/10/01 14:47:36 UTC
[jira] Commented: (CASSANDRA-1217) jmx: differentiate between
thread pools on the request paths and internal ones
[ https://issues.apache.org/jira/browse/CASSANDRA-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916877#action_12916877 ]
Hudson commented on CASSANDRA-1217:
-----------------------------------
Integrated in Cassandra #552 (See [https://hudson.apache.org/hudson/job/Cassandra/552/])
re-organize JMX into.db, .net, .internal, .request
patch by jbellis; reviewed by brandonwilliams for CASSANDRA-1217
> jmx: differentiate between thread pools on the request paths and internal ones
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-1217
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1217
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1217.txt, 1217.txt
>
>
> currently most thread pools are available in jmx under o.a.c.concurrent, with a scattering elsewhere.
> most thread pools on the request path are named -STAGE and most that are not are named -POOL, but this is not 100% consistent, and some are neither.
> I propose splitting these into two categories (removing .concurrent), one for request stages and one for internal pools, for ease of monitoring.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.