You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Rofi Uddin (JIRA)" <ji...@apache.org> on 2016/12/13 04:34:58 UTC

[jira] [Commented] (CASSANDRA-12121) CommitLogReplayException on Start Up

    [ https://issues.apache.org/jira/browse/CASSANDRA-12121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15744128#comment-15744128 ] 

Rofi Uddin commented on CASSANDRA-12121:
----------------------------------------

I was also able to reproduce this issue in 3.9. I think this issue occurs in following steps.
1. create a table with a mutable UDT field.
2. Insert records to the table along with mutable UDT field and it works fine. 
3. then restarting the node will give you this exception.

> CommitLogReplayException on Start Up
> ------------------------------------
>
>                 Key: CASSANDRA-12121
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12121
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Tom Burdick
>         Attachments: 000_epoch.cql, mutation7038154871517187161dat, sane_distribution.cql
>
>
> Using cassandra 3.7 and executing the attached .cql schema change files, then restarting one of the cassandra nodes in a cluster, I get this traceback
> I had to change the 000_epoch.cql file slightly to remove some important pieces, apologies if that makes this more difficult to verify.
> {noformat}
> ERROR [main] 2016-06-30 09:25:23,089 JVMStabilityInspector.java:82 - Exiting due to error while processing commit log during initialization.
> org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: Unexpected error deserializing mutation; saved to /tmp/mutation7038154871517187161dat.  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 java.nio.HeapByteBuffer[pos=0 lim=4 cap=4]
>         at org.apache.cassandra.db.commitlog.CommitLogReplayer.handleReplayError(CommitLogReplayer.java:616) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.commitlog.CommitLogReplayer.replayMutation(CommitLogReplayer.java:573) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.commitlog.CommitLogReplayer.replaySyncSection(CommitLogReplayer.java:526) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:412) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:228) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:185) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:165) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:314) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:585) [apache-cassandra-3.7.0.jar:3.7.0]
>         at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:714) [apache-cassandra-3.7.0.jar:3.7.0]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)