Cassandra 3.11 to 4.0 Rolling Upgrade: Where Does the Snapshot Rollback Window Actually Close?
A rolling upgrade from Cassandra 3.11 to 4.0 needs a rollback plan, and the unresolved question is where that plan stops working if the upgrade fails midway. The documented per-node sequence (drain, snapshot, then restart on 4.0) leaves pre-upgrade snapshots as hard links to existing SSTables, and the 3.11 binary can neither read 4.0-format SSTables nor repl
cassandra