You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jackson Chung (Created) (JIRA)" <ji...@apache.org> on 2012/01/10 22:39:39 UTC
[jira] [Created] (CASSANDRA-3720) Adding tombstone statistics to
cfstats
Adding tombstone statistics to cfstats
--------------------------------------
Key: CASSANDRA-3720
URL: https://issues.apache.org/jira/browse/CASSANDRA-3720
Project: Cassandra
Issue Type: New Feature
Reporter: Jackson Chung
Priority: Minor
given the number of tombstones can affect read performance (eg when "read the first column") , could we look into adding some stats monitoring of tombstone in cfstats or cfhistogram? Even if not for read performance, it's good to find a way to tell a "tombstone status" of a CF.
eg: similar to cfstats compaction row min/mean/max size section, a min/mean/max for tombstone count" ?
maybe nice also to check in cfhistogram, or maybe just have some open jmx methods?
ideas open
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-3720) Adding tombstone statistics to
cfstats
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3720:
--------------------------------------
Fix Version/s: 1.2
> Adding tombstone statistics to cfstats
> --------------------------------------
>
> Key: CASSANDRA-3720
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3720
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jackson Chung
> Priority: Minor
> Fix For: 1.2
>
>
> given the number of tombstones can affect read performance (eg when "read the first column") , could we look into adding some stats monitoring of tombstone in cfstats or cfhistogram? Even if not for read performance, it's good to find a way to tell a "tombstone status" of a CF.
> eg: similar to cfstats compaction row min/mean/max size section, a min/mean/max for tombstone count" ?
> maybe nice also to check in cfhistogram, or maybe just have some open jmx methods?
> ideas open
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-3720) Adding tombstone statistics to
cfstats
Posted by "Brandon Williams (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams resolved CASSANDRA-3720.
-----------------------------------------
Resolution: Duplicate
CASSANDRA-3515
> Adding tombstone statistics to cfstats
> --------------------------------------
>
> Key: CASSANDRA-3720
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3720
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jackson Chung
> Priority: Minor
> Fix For: 1.2
>
>
> given the number of tombstones can affect read performance (eg when "read the first column") , could we look into adding some stats monitoring of tombstone in cfstats or cfhistogram? Even if not for read performance, it's good to find a way to tell a "tombstone status" of a CF.
> eg: similar to cfstats compaction row min/mean/max size section, a min/mean/max for tombstone count" ?
> maybe nice also to check in cfhistogram, or maybe just have some open jmx methods?
> ideas open
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira