You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/06/24 05:30:46 UTC
[jira] [Commented] (CASSANDRA-8048) Add WARN for large resultsets
[ https://issues.apache.org/jira/browse/CASSANDRA-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14598813#comment-14598813 ]
Jonathan Ellis commented on CASSANDRA-8048:
-------------------------------------------
Created CASSANDRA-9643 to warn for large partitions and edited this title to make clear the distinction.
NB: Let's get our terminology consistent. You're worried about partitions, not rows.
> Add WARN for large resultsets
> -----------------------------
>
> Key: CASSANDRA-8048
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8048
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Adam Hattrell
>
> 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
(v6.3.4#6332)