[jira] Updated: (CASSANDRA-1217) jmx: differentiate between thread pools on the request paths and internal ones

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis updated CASSANDRA-1217:
--------------------------------------

    Attachment: 1217.txt

executors that deal w/ verb processing continue to be named _STAGE.

jmx grouped into .request and .internal for executors, and .db and .net for stuff we expose that are not.  this division isn't the only one possible -- you could make a case that StorageProxy belongs under .request, for instance -- but it's consistent.

took MessagingService.streamExecutor out of jmx, it was mainly just exposing a small subset of what we get from StreamingService, poorly.


> 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
>
>
> 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.