[
https://issues.apache.org/jira/browse/CASSANDRA-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403370#comment-17403370
]
Blake Eggleston commented on CASSANDRA-16850:
---------------------------------------------
bq. I was thinking that a single bad node could be a problem
what sort of scenario are you thinking of here? You can adjust thresholds per
node, which would be a better way to do per node adjustments if you really
wanted to
> 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: [email protected]
For additional commands, e-mail: [email protected]
