-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.3.5, 3.4.0
-
Component/s: None
-
None
-
Empty show more show less
I'm updating to 3.4.0 in COMPASS-4017 and I noticed when connected to compass shared data that every 30 seconds I’m seeing "Topology type: Replica Set (No Primary) is not writable" → "Topology type: Replica Set (With Primary) is writable".
The pattern seems to be 2 successful heartbeats for each server, no I never get a serverHeartbeatFailed and then:
topology [topology#0] changed: 22:36:41.278 ololog.js:143 type: [ReplicaSetWithPrimary] => [ReplicaSetNoPrimary] 22:36:41.279 ololog.js:143 error: [MongoNetworkError: connection 0 to compass-data-sets-shard-00-00-e06dc.mongodb.net:27017 timed out] => [MongoNetworkError: connection 1 to compass-data-sets-shard-00-02-e06dc.mongodb.net:27017 timed out]
This process repeats every 30 seconds. Does not happen on localhost with standalone, does happen with both compass shared data and free tier atlas deployments.
- causes
-
COMPASS-4192 Compass reconnect every 30 seconds
- Closed
- is related to
-
NODE-2385 client 3.4 gives "Server selection timed out", but 3.3.5 does not
- Closed
-
NODE-1742 Implement Connection Monitoring and Pooling spec
- Closed
-
COMPASS-3407 Log SDAM events in data-service
- Closed
- split from
-
COMPASS-4017 Update to node driver 3.4.0
- Closed