[
https://issues.apache.org/jira/browse/CASSANDRA-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626500#comment-16626500
]
Jordan West commented on CASSANDRA-14782:
-----------------------------------------
It turns out what I wanted exists already in a little known setting:
[https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/transport/Frame.java#L205-L216]
[https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/transport/Frame.java#L138.]
[~cnlwsu] mentioned it would be nice for this to be a hotprop so I am going to
repurpose this ticket for that.
> Large mutations can wreak havoc before being rejected by the commit log
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-14782
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14782
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jordan West
> Priority: Major
>
> Large mutations are rejected by the commit log
> (https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L254)
> but when {{totalSize}} is significantly greater than the
> {{MAX_MUTATION_SIZE}} the damage to the node may already done. Large
> mutations cause large buffers to be allocated and can lead to GC trashing and
> generally bad node health.
> It should be possible to set a size above which the native protocol rejects
> messages without materializing them into objects and passing them downstream.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
