[
https://issues.apache.org/jira/browse/CASSANDRA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763730#action_12763730
]
Jonathan Ellis commented on CASSANDRA-482:
------------------------------------------
+ public int getRunningTasks();
This is not worth the overhead in the commitlog executor.
+ public int getPoolSize();
+ public long getCompletedTasks();
What actionable information do these produce? I.e., what decision can you now
make with this data that you could not before?
> 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.
