Operational Defect Database

BugZero found this defect 77 days ago.

MongoDB | 2596527

Issue in failover process

Last update date:

3/9/2024

Affected products:

MongoDB Server

Affected releases:

7.0.3

Fixed releases:

No fixed releases provided.

Description:

Info

I have many 3 nodes of MongoDB replica set on Kubernetes, recently we had an incident in our data center that affected our MongoDB clusters, clusters can't do the failover process successfully, to reproduce this issue after the incident I set a NetworkPolicy to block Egress from secondary nodes to the primary node. after applying this Networkpolicy cluster don't have any issues maybe the network policy doesn't drop established connections..., but after I restart one of the MongoDB nodes cluster try to failover and change the primary(unreachable node) with one of the secondary nodes but after a while, it continuously switches primary to secondary and secondary to primary again.

Top User Comments

JIRAUSER1277456 commented on Sat, 9 Mar 2024 12:07:31 +0000: Hi Christopher  Thank you for your explanation, I will check these documents and share the result with you. JIRAUSER1265262 commented on Mon, 4 Mar 2024 15:48:15 +0000: Hi mhossini3458@gmail.com, Per our operations checklist,, we require full bidirectional network connectivity between all mongod instances. Please review and confirm if the issue persists. If you have questions, I'd encourage you to ask our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project. Christopher

Steps to Reproduce

Apply this Networkpolicy or block Egress traffic from the secondary pod to the primary pod // Networkpolicy apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: test-network-policy namespace: mw spec: podSelector: matchLabels: app.kubernetes.io/instance: x-mongo policyTypes: - Egress egress: - to: - ipBlock: cidr: 0.0.0.0/0 except: - 192.168.242.35/32 // (Primary pod IP address)

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Closed

Learn More

Search:

...