cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Capwell (Jira)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-16850) Add client warnings and abort to tombstone and coordinator reads which go past a low/high watermark
Date Mon, 16 Aug 2021 16:40:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Capwell updated CASSANDRA-16850:
--------------------------------------
    Description: 
We currently will abort queries if we hit too many tombstones, but its common that we would
want to also warn clients (client warnings) about this before we get that point; its also
common that different logic would like to be able to warn/abort about client options (such
as reading a large partition).  To allow this we should add a concept of low/high watermarks
(warn/abort) to tombstones and coordinator reads.

Another issue is that current aborts look the same as a random failure, so from an SLA point
of view it would be good to differentiate between user behavior being rejected and unexplained
issue.

  was:We currently will abort queries if we hit too many tombstones, but its common that we
would want to also warn clients (client warnings) about this before we get that point; its
also common that different logic would like to be able to warn/abort about client options
(such as reading a large partition).  To allow this we should add a concept of low/high watermarks
(warn/abort) to tombstones and coordinator reads.


> Add client warnings and abort to tombstone and coordinator reads which go past a low/high
watermark
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-16850
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16850
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability/Logging
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 4.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We currently will abort queries if we hit too many tombstones, but its common that we
would want to also warn clients (client warnings) about this before we get that point; its
also common that different logic would like to be able to warn/abort about client options
(such as reading a large partition).  To allow this we should add a concept of low/high watermarks
(warn/abort) to tombstones and coordinator reads.
> Another issue is that current aborts look the same as a random failure, so from an SLA
point of view it would be good to differentiate between user behavior being rejected and unexplained
issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message