Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <33395347.479401285862498501.JavaMail.jira@thor>
Date: Thu, 30 Sep 2010 12:01:38 -0400 (EDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1217) jmx: differentiate between
 thread pools on the request paths and internal ones
In-Reply-To: <24845303.15351277223176555.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-1217:
-------------------------------------------

cleaned up stage names to format like the others (MutationStage instead of MUTATION_STAGE).  Renamed REPAIR_STAGE to ReadRepair, and AE_SERVICE_STAGE to AntientropyStage.  (Turns out that ReadRepair actually isn't a verb-handling stage, it was misleadingly named before.)

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