[
https://issues.apache.org/jira/browse/CASSANDRA-21478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18094067#comment-18094067
]
Caleb Rackliffe commented on CASSANDRA-21478:
---------------------------------------------
The primary intent here was to make this something that operates at the level
of a local read, and is then reported to the coordinator (like the existing
guardrails around read size). In other words, we don't want an exorbitantly
expensive local read caused by pathological storage engine conditions to take
down an entire node. (Let me know if that helps...)
> Add a new guardrail around the number of SSTables per read
> ----------------------------------------------------------
>
> Key: CASSANDRA-21478
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21478
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/Guardrails
> Reporter: Caleb Rackliffe
> Assignee: Shlomit
> Priority: Normal
> Fix For: 6.x, 7.x
>
>
> While there is some prior art on this for SAI, which warns and then fails
> queries that touch too many SSTable indexes, the normal non-index read path
> does not have any guardrail for extremely aberrant cases where perhaps
> compaction falls behind and a small percentage of reads touch hundreds of
> SSTables. It might be nice for the server to be louder about this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
