You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "EDSON VICENTE CARLI JUNIOR (JIRA)" <ji...@apache.org> on 2018/11/28 12:04:00 UTC
[jira] [Created] (CASSANDRA-14914) Deserialization Error
EDSON VICENTE CARLI JUNIOR created CASSANDRA-14914:
------------------------------------------------------
Summary: Deserialization Error
Key: CASSANDRA-14914
URL: https://issues.apache.org/jira/browse/CASSANDRA-14914
Project: Cassandra
Issue Type: Bug
Environment: I use cassandra 3.9, but I tried to upgrade to 3.11 and nothing has changed.
Reporter: EDSON VICENTE CARLI JUNIOR
Fix For: 3.11.x
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.
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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org