Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-2387

Unexpected connection flapping

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: 3.3.5, 3.4.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • MongoDB Version:
      4.2.2

      Description

      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.

        Attachments

        1. Screenshot 2019-12-14 22.49.48.png
          Screenshot 2019-12-14 22.49.48.png
          1.21 MB
        2. sdam-compass.log
          42 kB

          Issue Links

            Activity

              People

              Assignee:
              lucas.hrabovsky Lucas Hrabovsky (Inactive)
              Reporter:
              lucas.hrabovsky Lucas Hrabovsky (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: