Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-4676

MongoUtilIT test failure - unable to connect to primary


      Recently the MongoUtilIT test has begun to fail on GH actions. From the logs it appears that the election of the primary is happening after the tests have started and this delay is leading to random test failures.

      2022-02-04T13:13:08.2587348Z io.debezium.DebeziumException: Unable to find primary from MongoDB connection, got '[ServerDescription{address=localhost:27017, type=REPLICA_SET_SECONDARY, state=CONNECTED, ok=true, minWireVersion=0, maxWireVersion=6, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTimeNanos=15549218, setName='rs0', canonicalAddress=, hosts=[], passives=[], arbiters=[], primary='', tagSet=TagSet{[]}, electionId=7fffffff0000000000000001, setVersion=1, topologyVersion=null, lastWriteDate=Fri Feb 04 13:13:07 UTC 2022, lastUpdateTimeNanos=142633760070}]'

      and later after the test has fired, the logs show

      2022-02-04T13:13:09.1242239Z 13:13:09.122 mongo12022-02-04T13:13:09.122+0000 I STORAGE  [rsSync] createCollection: config.transactions with generated UUID: 2f403cbc-cd4d-49d1-9187-74d19ae2d149
      2022-02-04T13:13:09.1291587Z 13:13:09.128 mongo12022-02-04T13:13:09.127+0000 I REPL     [rsSync] transition to primary complete; database writes are now permitted

            ccranfor@redhat.com Chris Cranford
            ccranfor@redhat.com Chris Cranford
            0 Vote for this issue
            3 Start watching this issue