[
https://issues.apache.org/jira/browse/CASSANDRA-14782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627536#comment-16627536
]
Chris Lohfink commented on CASSANDRA-14782:
-------------------------------------------
bq. Is this something that an operator would like to change while the database
is running
Yes, definitely. Even if the max was lowered to 64mb.
bq. What happens when they don't match across various nodes in the cluster?
Only the coordinator would throw it away, if large request goes to a different
host it would still send the large mutation to the replicas to get thrown away
when applied to commit log. This value does not effect inter node messages,
only CQL.
> Make DatabaseDescriptor.getNativeTransportMaxFrameSize() a hotprop
> ------------------------------------------------------------------
>
> 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]
