You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Jonas Borgström <jo...@borgstrom.se> on 2017/03/18 13:21:15 UTC

Corrupt SSTable after dropping column

Hi,


It seems like dropping a column can cause a "java.io.IOException: 
Corrupt empty row found in unfiltered partition" exception when existing 
SSTables are later compacted.

This seems to happen with all Cassandra 3.x versions and is very easy to 
replicate. I've created a jira with all the details:

https://issues.apache.org/jira/browse/CASSANDRA-13337

This is extra problematic with Cassandra < 3.10 where nodes will fail to 
start once this happens.

Have anyone else seen this?

/ Jonas