cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Malte Pickhan (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-12839) CommitLogReplayException: Unexpected error deserializing mutation
Date Wed, 02 Nov 2016 12:44:58 GMT

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

Malte Pickhan edited comment on CASSANDRA-12839 at 11/2/16 12:44 PM:
---------------------------------------------------------------------

Sorry, I cannot attach it since the file is already removed. No, we didn't start it like that.
We just dropped the commitlog and bootstrapped a fresh node to replace it. After that we went
through all nodes of the cluster and drained it in order to get rid of potentially corrupted
commitlogs.


was (Author: malpi):
Sorry, I cannot attach it since the file is already removed. No, we didn't start it like that.
We just dropped the commitlog and bootstrapped a fresh node to replace it.

> CommitLogReplayException: Unexpected error deserializing mutation
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-12839
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12839
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Ubuntu, Cassandra 3.7, RF3
>            Reporter: Malte Pickhan
>            Priority: Blocker
>
> We wanted to run a *nodetool repair*  on the affected node. This was not possible due
to CASSANDRA-12694.
> Therefore we wanted to shutdown the node in order to run scrubsstables. After this was
done, bootstrapping the node was not possible anymore. It was not possible since it wasn't
able to replay the commitlog. Unfortunately we didn't run a drain before.
> {quote}
> org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: Unexpected
error deserializing mutation; saved to /tmp/mutation4616409546670104469dat.  This may be caused
by replaying a mutation against a table with the same name but incompatible schema.  Exception
follows: java.io.IOError: java.io.IOException: Corrupt empty row found in unfiltered partition
> {quote}
> Two days before that, we actually did some modification on the table and dropped a column.



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

Mime
View raw message