[ https://issues.apache.org/jira/browse/CASSANDRA-14914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737136#comment-16737136 ]
EDSON VICENTE CARLI JUNIOR commented on CASSANDRA-14914: -------------------------------------------------------- No, I not used no one custom timestamp into my application > Deserialization Error > --------------------- > > Key: CASSANDRA-14914 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14914 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Core > Environment: I use cassandra 3.9, but I tried to upgrade to 3.11 and > nothing has changed. > Reporter: EDSON VICENTE CARLI JUNIOR > Priority: Critical > Fix For: 3.11.x > > Attachments: mutation4465429258841992355dat > > > > I have a single cassandra, now this error appears when I start the server: > {code:java} > ERROR 11:18:45 Exiting due to error while processing commit log during > initialization. > org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: > Unexpected error deserializing mutation; saved to > /tmp/mutation4787806670239768067dat. 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: A local > deletion time should not be negative > {code} > If I delete all the commitlog and saved_cached files the server goes up, but > the next day when I reboot the cassandra, the error occurs again. > The file mutationDDDDDDDDDDdat change name for each restart. I attachament a > example mutation file . > What's wrong? How to make cassandra stable again? > -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org