[jira] [Commented] (CASSANDRA-8048) Add WARN for large resultsets

["Michael Semb Wever (Jira)" <ji...@apache.org>]

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

Michael Semb Wever commented on CASSANDRA-8048:
-----------------------------------------------

Closing this out as "won't do" given cassandra.yaml settings for {{max_value_size}}, {{column_value_size_warn_threshold}} and {{column_value_size_fail_threshold}}.

> Add WARN for large resultsets
> -----------------------------
>
>                 Key: CASSANDRA-8048
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8048
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Legacy/Observability
>            Reporter: Adam Hattrell
>            Priority: Normal
>
> Similarly to how we warn on excessive tombstones or large batches - it would be useful to warn if we come across a large row over a specific threshold.
> If not too intrusive it could provide us with a smoking gun for gc thrashing type issues.
> To put some meat on the bones - I've recently seen someone store a 1Gb blob and then try to work round it by splitting it into 3 columns of 330 Mb each.  Neither gave particularly good performance.
> On the opposite side of the coin - a large number of columns grabbed at once can also lead to problems.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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