[CASSANDRA-14782] Make DatabaseDescriptor.getNativeTransportMaxFrameSize() a hotprop

• Type: Bug
• Status: Open
• Priority: Normal
• Resolution: Unresolved
• Component/s: Legacy/Observability, Local/Config
• Severity: Normal
• Assignee: Unassigned
• Reporter: Jordan West
• Created: 21/Sep/18 20:37
• Updated: 10/Jan/20 16:06

Description

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. 

 

Issue Links

• relates to: CASSANDRA-14433 DoS attack through PagingState
• relates to: CASSANDRA-14781 Log message when mutation passed to CommitLog#add(Mutation) is too large is not descriptive enough