Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Operability
-
Normal
-
All
-
None
-
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.
Attachments
Issue Links
- links to