[CASSANDRA-14781] Log message when mutation passed to CommitLog#add(Mutation) is too large is not descriptive enough

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta1, 4.0
• Component/s: Consistency/Hints, Local/Commit Log, Messaging/Client
• Labels: protocolv5
• Severity: Normal
• Since Version: 4.0-beta1

Source Control Link

https://github.com/apache/cassandra/commit/d3dadcd6f3bbde471e972f8332eb62de0f2d4aae

• Assignee: n.v.harikrishna Assign to me
• Reporter: Jordan West

Authors

n.v.harikrishna

Reviewers

Chris Lohfink, Jordan West

• Created: 21/Sep/18 19:29
• Updated: 30/Apr/21 06:46
• Resolved: 04/May/20 18:33

Description

When hitting https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/db/commitlog/CommitLog.java#L256-L257, the log message produced does not help the operator track down what data is being written. At a minimum the keyspace and cfIds involved would be useful (and are available) – more detail might not be reasonable to include. 

Issue Links

• is related to: CASSANDRA-14782 Make DatabaseDescriptor.getNativeTransportMaxFrameSize() a hotprop
• is related to: CASSANDRA-12231 Make large mutations easier to find
• relates to: CASSANDRA-15741 Mutation size exceeds max limit - clients get timeout?