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
What happened?
The latest release of Medusa, v0.14.0, broke restore mappings by selecting the same node (the last one) as source for mapping to each of the existing pods.
This results in broken clusters after a restore.
Did you expect to see something different?
Restore mappings should be done consistently with one source node mapping to a single target node. This was working correctly in Medusa v0.13.4.
Environment
K8ssandra Operator version:
v1.4.0
The text was updated successfully, but these errors were encountered:
What happened?
The latest release of Medusa, v0.14.0, broke restore mappings by selecting the same node (the last one) as source for mapping to each of the existing pods.
This results in broken clusters after a restore.
Did you expect to see something different?
Restore mappings should be done consistently with one source node mapping to a single target node. This was working correctly in Medusa v0.13.4.
Environment
K8ssandra Operator version:
v1.4.0
The text was updated successfully, but these errors were encountered: