You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2011/02/16 02:20:57 UTC
[jira] Created: (CASSANDRA-2171) Record and expose flush rate per
CF
Record and expose flush rate per CF
-----------------------------------
Key: CASSANDRA-2171
URL: https://issues.apache.org/jira/browse/CASSANDRA-2171
Project: Cassandra
Issue Type: Improvement
Reporter: Stu Hood
Assignee: Stu Hood
Fix For: 0.8
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
[jira] Commented: (CASSANDRA-2171) Record and expose flush rate per
CF
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (CASSANDRA-2171) Record and expose flush rate per
CF
Posted by "Alan Liang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Liang updated CASSANDRA-2171:
----------------------------------
Attachment: expose_flush_rate_per_cf_patch.diff
Attached patch to record flush rate per CF. Exposed this rate through JMX.
> 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: Stu Hood
> 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
[jira] [Resolved] (CASSANDRA-2171) Record and expose flush rate per
CF
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood resolved CASSANDRA-2171.
---------------------------------
Resolution: Not A Problem
Resolving due to lack of demand, and the changing landscape caused by Leveled compaction.
> Record and expose flush rate per CF
> -----------------------------------
>
> Key: CASSANDRA-2171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2171
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stu Hood
> Assignee: Alan Liang
> Priority: Minor
> Fix For: 0.8.5
>
> 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
[jira] [Updated] (CASSANDRA-2171) Record and expose flush rate per
CF
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2171:
--------------------------------------
Priority: Minor (was: Major)
> Record and expose flush rate per CF
> -----------------------------------
>
> Key: CASSANDRA-2171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2171
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stu Hood
> Assignee: Alan Liang
> Priority: Minor
> Fix For: 0.8.1
>
> 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
[jira] Commented: (CASSANDRA-2171) Record and expose flush rate per
CF
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004794#comment-13004794 ]
Stu Hood commented on CASSANDRA-2171:
-------------------------------------
> It's not clear to me what kind of data is useful for CASSANDRA-2156. Why a sliding window?
If you flushed x MB in the last 30 minutes, you need to compact at a proportionate rate. There would also have to be a lower bound to prevent compaction from stopping completely.
> 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
[jira] Assigned: (CASSANDRA-2171) Record and expose flush rate per
CF
Posted by "Alan Liang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Liang reassigned CASSANDRA-2171:
-------------------------------------
Assignee: Alan Liang (was: Stu Hood)
> 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