卡桑德拉错误。未筛选分区中发现的损坏空行

Question

当我启动一个cassandra实例时，我得到了一个错误。你知道我怎么能修好它吗？

primecast-cassandra_1            | org.apache.cassandra.db.commitlog.CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation; saved to /tmp/mutation6385168154232968395dat.  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
primecast-cassandra_1            |  at org.apache.cassandra.db.commitlog.CommitLogReader.readMutation(CommitLogReader.java:410) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.db.commitlog.CommitLogReader.readSection(CommitLogReader.java:343) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.db.commitlog.CommitLogReader.readCommitLogSegment(CommitLogReader.java:202) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.db.commitlog.CommitLogReader.readAllFiles(CommitLogReader.java:85) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.db.commitlog.CommitLogReplayer.replayFiles(CommitLogReplayer.java:135) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.db.commitlog.CommitLog.recoverFiles(CommitLog.java:187) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.db.commitlog.CommitLog.recoverSegmentsOnDisk(CommitLog.java:167) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:323) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:601) [apache-cassandra-3.9.jar:3.9]
primecast-cassandra_1            |  at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:730) [apache-cassandra-3.9.jar:3.9]

Answer 1

运行nodetool describecluster。您可能会看到多个模式版本。如果您有多个架构版本：

Cassandra

• Delete

1. 停止提交日志，保存的缓存(如果需要帮助，请告诉我)
2. 启动Cassandra
3. Run nodetool describecluster，看看现在是否只有

模式版本

以滚动的方式在所有节点中进行清理和重新启动。

您是否正在进行常规的架构更改？如果是，则可能是架构更改没有足够快地到达所有节点。

Answer 2

有趣的是，节点工具排水系统正在解决这个问题。不知道它是怎么工作的

螺杆式排水

该命令可能会将memtable刷新为sstable。