Petr Hála

> maybe sizing down nodes when doubling? We definitely can do that, good idea, it will be still be a cost increase, but much smaller

> Can you explain why? do you mean headroom in terms of overload? > Do you have a link to example? We need to have additional nodes due to disruption...

There are a few PRs open for elastic cloud that make use of that option, I think the subject of this issue is resolved.

It would nice to include update to `docs/dev/testing.md` as well

> > @tgrabiec how about documentation? Should we update e.g. https://docs.scylladb.com/manual/stable/operating-scylla/nodetool-commands/decommission.html and https://docs.scylladb.com/manual/stable/operating-scylla/nodetool-commands/removenode.html ? > > We could, or we could treat it as implementation detail. They already can be...

Noted, will schedule it after 2025.1 testing work is done

> @pehala - @temichus is on PTO, please take it with someone in his team or just implement it: > `rf_rack_valid_keyspaces: true` in scylla.yaml , it's important for 2025.1.0. I...

> FYI, while working on this in dtest, seems like the flow of decommission is not yet fully defined. > > I.e. we can't decommission a node before RF is...

> We discussed it today and the plan is to implement [scylladb/scylladb#23426](https://github.com/scylladb/scylladb/issues/23426). @mykaul Not sure how much sense it would make to test rack == #racks for 2025.1.0 if boostrap/decomission...

> [@pehala](https://github.com/pehala) - I think it is more on your end than mine. I looked at the code trying to figure out if is closer to search-replace-tweak activity or more...