[
https://issues.apache.org/jira/browse/CASSANDRA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763740#action_12763740
]
Jonathan Ellis commented on CASSANDRA-482:
------------------------------------------
from irc:
> i can see runningtasks being useful actually, to see how close you are to an
> executor getting swamped, and completedtasks, so rrd can turn it into a rate
> which is useful for system health. but poolsize is just not useful.
let's do this.
rename getRunningTasks to getActiveCount so it just leverages the TPE version.
make the CLE version always return 1. (not strictly accurate, but it's
basically useless info for a non-pooled executor.)
make the completed count in CLE a volatile long instead of atomic -- you only
need an Atomic variable if multiple threads are going to update it which is not
the case here.
> Expose out additional metrics for the thread pools: active threads, pool
> size, and completed tasks
> --------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-482
> URL: https://issues.apache.org/jira/browse/CASSANDRA-482
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: 0.5
> Reporter: Sammy Yu
> Assignee: Sammy Yu
> Attachments:
> 0001--CASSANDRA-482-Expose-out-additional-metrics-for-th.patch
>
>
> It would be nice to expose out additional metrics in the threadpools via
> nodeprobe's tpstats to understand how busy the system is.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
