cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyuben Todorov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8880) Add metrics to monitor the amount of tombstones created
Date Wed, 04 Mar 2015 18:43:38 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347346#comment-14347346
] 

Lyuben Todorov commented on CASSANDRA-8880:
-------------------------------------------

Do we want to increment the number of tombstones written from both the tombstones added to
memtables and sstables, or only the ones that make it all the way to sstables? Im guessing
it would be the former based on how tracing works, specifically if it's only sstables we could
end up with tracing showing tombstones being fetched but with the metric showing 0 written
tombstones. 

Also, what version should I target with the patch? Currently I'm going for 2.1.

> Add metrics to monitor the amount of tombstones created
> -------------------------------------------------------
>
>                 Key: CASSANDRA-8880
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8880
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Michaël Figuière
>            Priority: Minor
>
> AFAIK there's currently no way to monitor the amount of tombstones created on a Cassandra
node. CASSANDRA-6057 has made it possible for users to figure out how many tombstones are
scanned at read time, but in write mostly workloads, it may not be possible to realize if
some inappropriate queries are generating too many tombstones.
> Therefore the following additional metrics should be added:
> * {{writtenCells}}: amount of cells that have been written
> * {{writtenTombstoneCells}}: amount of tombstone cells that have been written
> Alternatively these could be exposed as a single gauge such as {{writtenTombstoneCellsRatio}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message