Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14914

Deserialization Error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Urgent
    • Resolution: Cannot Reproduce
    • 3.11.x
    • Legacy/Core
    • None
    • I use cassandra 3.9, but I tried to upgrade to 3.11 and nothing has changed.

    • Critical

    Description

       
      I have a single cassandra, now this error appears when I start the server:

      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
      

      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?

       

      Attachments

        1. mutation4465429258841992355dat
          0.1 kB
          EDSON VICENTE CARLI JUNIOR

        Activity

          People

            Unassigned Unassigned
            gandbranco EDSON VICENTE CARLI JUNIOR
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: