Hi Team For the cassandra 5, upgrade storage_compatibility_mode is mandated to be used as follows
- Do a rolling upgrade to 5.0 where 2038 will still be the limit. At this point, the node won't write anything incompatible with Cassandra 4.x, and you would still be able to rollback to that version. - Do a rolling restart setting storage_compatibility_mode=UPGRADING. Once all nodes are in storage version 5, 2106 will become the new limit. - Do a rolling restart setting storage_compatibility_mode=NONE. Now mixed 2038 and 2106 nodes are no longer possible. This looks a good way to do a safe upgrade with additional advantage to do a rollback. But this also introduces an issue where multiple restarts are required during upgrade. For large clusters it could be an issue to have multiple restarts. Is there any other way around this so we can avoid multiple restarts? Regards Manish
