Jason
Jason
I did a bit more investigation and it is failing on the second call to clusterManagerSetSlot in clusterManagerMoveSlot where it sets it on the source node. Would it be ok...
We see this issue on upgrade from redis 7.0 to valkey 7.2 (or 8.0.0-rc1). The scenario is: - all nodes start at 7.0 (so no shard-id in cluster nodes file)...
I backported https://github.com/valkey-io/valkey/pull/573 on top of 8.0.0-rc1 and I still see cases during upgrade before all the nodes have been upgraded where the 8.0.0 nodes do not have consistent shard-ids...
I will try next week and get back to you.
@bentotten I do still see issues when pulling #778. If you have a cluster running redis 7.0, where cluster nodes file has no shard-id, then shutdown all 7.0 nodes and...
@madolson, should I open an issue for the upgrade from 7.0 corruption I described above?
Maybe you can make something work by saving as aof and setting 'aof-use-rdb-preamble no'.
Authentication modules would be useful for sentinel. The org I work for has a custom auth module that would be useful to also use for sentinel.
Just adding another vote for this feature to be included. Our telco customer are always insisting on rollback capabilities in our deployments.
Is there a command that can be used to check if new features are in use that would prohibit downgrade?