[
https://issues.apache.org/jira/browse/CASSANDRA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745283#action_12745283
]
Michael Greene commented on CASSANDRA-369:
------------------------------------------
The code looks good after explanation and works when exercised. I was
surprised that running stress against against a single node cluster, probing
that node only ever gives values of 0,1, or 2 for the commitlog--it seems like
it should have a deeper queue then that.
+1
> Expose commitlog queue size
> ---------------------------
>
> Key: CASSANDRA-369
> URL: https://issues.apache.org/jira/browse/CASSANDRA-369
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.4
>
> Attachments: 369-v2.patch, 369.patch
>
>
> Need to expose queue size of CommitLogExecutorService via jmx. Probably we
> can extract the mbean code from DebuggableThreadPoolExecutor and reuse it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
