You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming a Redis Cluster managed by the operator was upgraded from Version A to Version B. However, due to various reasons, this upgrade now needs to be rolled back. Given that the operator is subject to Redis's downgrade limitations (such as incompatible RDB versions, which can make downgrading impossible), what would be the advised method to revert to Version A?
Can the operator recognize that the target version is an older, incompatible version and, based on this information, clear the persistent volumes to allow a fresh start for the Redis process followed by loading a previously saved and compatible snapshot?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Assuming a Redis Cluster managed by the operator was upgraded from Version A to Version B. However, due to various reasons, this upgrade now needs to be rolled back. Given that the operator is subject to Redis's downgrade limitations (such as incompatible RDB versions, which can make downgrading impossible), what would be the advised method to revert to Version A?
Can the operator recognize that the target version is an older, incompatible version and, based on this information, clear the persistent volumes to allow a fresh start for the Redis process followed by loading a previously saved and compatible snapshot?
Beta Was this translation helpful? Give feedback.
All reactions