issue afer cross cluster failover and switch from unmanaged to managed cluster
General
Escalation
General
Escalation
Description
I did the same setup as in blogpost "Disaster Recovery for MongoDB on Kubernetes" with the only difference that after I did failover I also changed "unmanaged: true" to "unmanaged: false" on the second cluster. The result is that my cluster is stuck in "initializing" state.
I did the same setup as in blogpost "Disaster Recovery for MongoDB on Kubernetes" with the only difference that after I did failover I also changed "unmanaged: true" to "unmanaged: false" on the second cluster.
The result is that my cluster is stuck in "initializing" state.
Here's how it looks:
Operator logs:
Primary for replicas are elected: