[
https://issues.apache.org/jira/browse/CASSANDRA-8527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295773#comment-16295773
]
Jon Haddad commented on CASSANDRA-8527:
---------------------------------------
It's a little odd that we'd still report back "0 tombstones" when in fact there
are tombstones. I'd love to see the number of range tombstones separately
tracked and reported as part of this patch.
For discussion's sake, I'd like to point out that this patch changes the
behavior of the tombstone warning and failure thresholds:
{code}
- if (tombstones > failureThreshold &&
respectTombstoneThresholds)
+ if (tombstones + deletedRows > failureThreshold &&
respectTombstoneThresholds)
{code}
I haven't given this much thought yet about if it's the "right way", but it's
important to note as it can significantly change the behavior of when queries
warn and fail.
> Account for range tombstones wherever we account for tombstones
> ---------------------------------------------------------------
>
> Key: CASSANDRA-8527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8527
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Alexander Dejanovski
> Fix For: 4.x
>
> Attachments: CASSANDRA-8527.diff
>
>
> As discussed in CASSANDRA-8477, we should make sure the tombstone thresholds
> also apply to range tombstones, since they poses the same problems than cell
> tombstones.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
