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

Flaky tests in MongoDB connector

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: mongodb-connector
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Run any of the following:

      mvn clean install -B -pl debezium-connector-mongodb -am -Passembly -Dformat.formatter.goal=validate -Dformat.imports.goal=check
      mvn clean install -B -pl debezium-connector-mongodb -am -Passembly -Dformat.formatter.goal=validate -Dformat.imports.goal=check -Dversion.mongo.server=4.0
      mvn clean install -B -pl debezium-connector-mongodb -am -Passembly -Dformat.formatter.goal=validate -Dformat.imports.goal=check -Dversion.mongo.server=3.2
      
      Show
      Run any of the following: mvn clean install -B -pl debezium-connector-mongodb -am -Passembly -Dformat.formatter.goal=validate -Dformat.imports.goal=check mvn clean install -B -pl debezium-connector-mongodb -am -Passembly -Dformat.formatter.goal=validate -Dformat.imports.goal=check -Dversion.mongo.server=4.0 mvn clean install -B -pl debezium-connector-mongodb -am -Passembly -Dformat.formatter.goal=validate -Dformat.imports.goal=check -Dversion.mongo.server=3.2

      Description

      MongoDB connector includes a flaky test that can fail depending on system load.

      -------------------------------------------------------------------------------
      Test set: io.debezium.connector.mongodb.MongoDbConnectorIT
      -------------------------------------------------------------------------------
      Tests run: 22, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 166.526 s <<< FAILURE! - in io.debezium.connector.mongodb.MongoDbConnectorIT
      shouldConsumeTransaction(io.debezium.connector.mongodb.MongoDbConnectorIT)  Time elapsed: 5.36 s  <<< FAILURE!
      java.lang.AssertionError: Unable to connect to primary after 3 errors trying to storing documents: com.mongodb.MongoCommandException: Command failed with error 24 (LockTimeout): 'Unable to acquire lock '{8276363597614759335: Database, 1358834569973677479}' within a max lock request timeout of '5ms' milliseconds.' on server localhost:27017. The full response is {"errorLabels": ["TransientTransactionError"], "operationTime": {"$timestamp": {"t": 1584653160, "i": 4}}, "ok": 0.0, "errmsg": "Unable to acquire lock '{8276363597614759335: Database, 1358834569973677479}' within a max lock request timeout of '5ms' milliseconds.", "code": 24, "codeName": "LockTimeout", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1584653160, "i": 4}}, "signature": {"hash": {"$binary": "AAAAAAAAAAAAAAAAAAAAAAAAAAA=", "$type": "00"}, "keyId": {"$numberLong": "0"}}}}
      	at io.debezium.connector.mongodb.MongoDbConnectorIT.lambda$connectionErrorHandler$35(MongoDbConnectorIT.java:1018)
      	at io.debezium.connector.mongodb.MongoDbConnectorIT.storeDocumentsInTx(MongoDbConnectorIT.java:971)
      	at io.debezium.connector.mongodb.MongoDbConnectorIT.shouldConsumeTransaction(MongoDbConnectorIT.java:765)
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ccranfor Chris Cranford
                Reporter:
                hashhar Ashhar Hasan
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: