[
https://issues.apache.org/jira/browse/CASSANDRA-12839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628801#comment-15628801
]
Stefan Podkowinski commented on CASSANDRA-12839:
------------------------------------------------
Can you attach the reported mutationXYdat file? Did you start Cassandra
afterwards using the {{-Dcommitlog.ignorereplayerrors}} flag or how did you
proceed with the situation?
> Replaying commitlog doesn't work
> --------------------------------
>
> 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)
