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

David Capwell commented on CASSANDRA-16850:
-------------------------------------------

bq. You can adjust thresholds per node

Thanks for pointing that out, didn't think about it.  My concern was cases 
where a single node is very different than others, causing one of the aborts to 
get hit when we don't want it to, so thought an opt-out would allow time to 
fix; but since we can always bump that specific check bounds we don't need to 
disable checks all together.

I left it so we can opt-out at the coordinator level

> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to