[
https://issues.apache.org/jira/browse/CASSANDRA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004190#comment-13004190
]
Jonathan Ellis commented on CASSANDRA-2171:
-------------------------------------------
It's not clear to me what kind of data is useful for CASSANDRA-2156. Why a
sliding window?
If a sliding window is the way to go, then I'd prefer to use a subclass of
AbstractStatsDeque than a CSLM. We used to have one
(https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.5/src/java/org/apache/cassandra/utils/TimedStatsDeque.java
-- not 100% sure that's the most recent version) before we pulled sliding
window stats out of the rest of Cassandra -- expensive to maintain and not
actually substantially more useful than simpler metrics, which is one reason I
want to make sure we're not violating YAGNI here.
> Record and expose flush rate per CF
> -----------------------------------
>
> Key: CASSANDRA-2171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2171
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.8
> Reporter: Stu Hood
> Assignee: Alan Liang
> Fix For: 0.8
>
> Attachments: expose_flush_rate_per_cf_patch.diff
>
>
> In order to automatically throttle compaction to some multiple of the flush
> rate, we need to record the flush rate across the system. Since this might be
> useful information on a per CF basis, this ticket will deal with recording
> the flush rate in the CFStore object, and exposing it via JMX.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
