[
https://issues.apache.org/jira/browse/CASSANDRA-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-3515:
--------------------------------------
Summary: track tombstone statistics (was: add tombstones thats been
filtered in cfhistograms)
We could also count tombstones-per-row during compaction and store the
histogram in the metadata component, than to count tombstones seen during reads.
Not *quite* as direct a red flag, since a heavily tombstoned row *could* be
just fine if you're doing name-based queries, but a lot easier to implement.
It also has the benefit of being able to get stats w/o having to wait for reads
to warm things up.
(CASSANDRA-1123 would give us the tools to build more fine-grained stats on a
per-query basis.)
> track tombstone statistics
> --------------------------
>
> Key: CASSANDRA-3515
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3515
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jackson Chung
> Priority: Minor
> Fix For: 1.2
>
>
> i think summary says it all, but see further:
> {noformat}
> driftx x: I guess we could add a histogram of how many tombstones we
> filtered on a read
> driftx x: @action: go for it in that context
> action jackson: thx!
> mdennis x: +1 on histogram of filtered tombstones
> driftx x: definitely useful for diagnosing the queue-like case
> driftx x: the histogram I mea
> {noformat}
--
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
