Issue with Replication Alteration During K8ssandra v1 to K8ssandra-Operator Migration about k8ssandra HOT 2 CLOSED

Hi @vcanuel,

However, when I implement these changes, each operator attempts to alter the replication settings within their own data center through the MigrationManager.

K8ssandra v1 shipped with cass-operator as the only operator. I don't think it should attempt to modify the replication by itself if you remove the externalDatacenter entries on the k8ssandra-operator side.

Could you be more specific about your installation for both DCs and indicate which operator instances are triggering the replication changes?

In any case, I'd recommend to turn off the deployment of the operator that is responsible for the DC which will be decommissioned and perform the changes in the K8ssandraCluster object. You can then delete the Cassandra statefulsets in the decommissioned DC and the associated PVCs/PVs.

from k8ssandra.

Hi,

Thank you for your recommendation. We have since resolved the issue by decommissioning dc1, so further investigation into the original problem isn't possible. Your insights might be helpful for similar situations in the future. We can close this issue now.

Best regards,

Vincent.

from k8ssandra.