[CASSANDRA-12916] Broken UDT muitations loading from CommitLog

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 3.10
• Component/s: Legacy/Local Write-Read Paths
• Labels: patch

Environment

Cassandra 3.9

• Severity: Critical
• Assignee: Sam Tunnicliffe
• Reporter: Sergey Dobrodey

Authors

Sam Tunnicliffe

Reviewers

Sam Tunnicliffe

• Created: 16/Nov/16 09:24
• Updated: 16/Apr/19 09:30
• Resolved: 22/Nov/16 17:03

Description

UDT mutatitions seems to be broken. Simple example is attached. After steps from it, restart cassandra and during commit log reading it will fail with error:

ERROR 09:34:46 Exiting due to error while processing commit log during initialization.
org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation; saved to /tmp/mutation6087238241614604390dat. This may be caused by replaying a mutation against a table with the same name but incompatible schema. Exception follows: org.apache.cassandra.serializers.MarshalException: Not enough bytes to read 0th field data

I resolved this problem, so my patch is in attachment.

Issue Links

• duplicates: CASSANDRA-12121 CommitLogReplayException on Start Up