Yelp rebuilds corrupted Cassandra cluster using its data streaming architecture
For those that care about <i>how</i> it got corrupted:<p><a href="https:&#x2F;&#x2F;engineeringblog.yelp.com&#x2F;2023&#x2F;01&#x2F;rebuilding-a-cassandra-cluster-using-yelps-data-pipeline.html#data-corruption-overview" rel="nofollow noreferrer">https:&#x2F;&#x2F;engineeringblog.yelp.com&#x2F;2023&#x2F;01&#x2F;rebuilding-a-cassan...</a><p>&gt; The investigation around the exception revealed that at-least one of the SSTable (Sorted String Table) rows was unordered, which caused the compaction operation to fail. SSTables are immutable files that are always sorted by the primary key<p>This was just... a bug in Cassandra? Is there anyone that can shed light on this? There seem to be plenty of people using Cassandra at scale -- is constantly repairing it normal practice?