On Fri, 17 Mar 2023 at 17:24, Brandon Williams <dri...@gmail.com> wrote:
> On Fri, Mar 17, 2023 at 9:25 AM Mick Semb Wever <m...@apache.org> wrote: > > Question/Suggestion: should we improve gossip to include what the oldest > format a node has, and ensure newer versioned node joining fail/warn if it > does > not support that older format? That is, should we give a clear > signal back to operators that their rolling upgrade is not going to work > smoothly, that they are > going to hit nodes they will need to stop and do > upgradesstables on (leaving them in a state of mix-versions and nodes busy > upgrading…) > > We already have this (even in 3.0!) to facilitate dropping compact > storage: > https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/gms/ApplicationState.java#L59 Nice! So is there appetite for such a patch to fail or warn (guardrail?) to prevent a node running on a new version that does not support sstable formats existing on other nodes?
