After MongoDB v5.x to v6.x upgrade, getting replica set network errors

Other MongoDB Topics
1

Replica set with combination of GCP servers and on-prem server
Current version: 5.0.20
GCP running on Centos 7.9
On-prem running on Redhat8
After upgrading to MongoDB v6.0.14, getting network error on the on-prem server
GCP servers can communicate with each other, but the on-prem server can’t communicate with the GCP servers.
Getting network error.
I downgrade the on-prem server to v5.0.20 again and it can communicate with the GCP servers again.

{“t”:{“$date”:“2024-03-26T08:22:42.717-04:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22566, “ctx”:“ReplicaSetMonitor-TaskExecutor”,“msg”:“Ending connection due to bad connection status”,“attr”:{“hostAndPort”:“preprod01-us-east1-mongodb-server03.gcp.llbean.com:27017”,“error”:“CallbackCanceled: Callback was canceled”,“numOpenConns”:1}}
{“t”:{“$date”:“2024-03-26T08:22:42.717-04:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22576, “ctx”:“ReplicaSetMonitor-TaskExecutor”,“msg”:“Connecting”,“attr”:{“hostAndPort”:“preprod01-us-east1-mongodb-server03.gcp.llbean.com:27017”}}

Can someone please help ?

Thanks !

Sally

2

Hello @Sally_Choo,

Following our upgrade from 5.0 to 6.0, we have a problem that is very similar to the previous one. 2 servers in a specific private zone and an on-prem server. We have the same connection errors on our on-prem server.
Were you able to resolve your problem? (without going back to version 5.x)

Thanks
Alex