mongo 2.18.2 → 2.19.3

data/spec/spec_tests/data/sdam_integration/cancel-server-check.yml

@@ -1,96 +0,0 @@
-# Test SDAM error handling.
-runOn:
-  # General failCommand requirements (this file does not use appName
-  # with failCommand).
-  - minServerVersion: "4.0"
-    topology: ["replicaset"]
-  - minServerVersion: "4.2"
-    topology: ["sharded"]
-
-database_name: &database_name "sdam-tests"
-collection_name: &collection_name "cancel-server-check"
-
-data: []
-
-tests:
-  - description: Cancel server check
-    clientOptions:
-      retryWrites: true
-      heartbeatFrequencyMS: 10000
-      # Server selection timeout MUST be less than heartbeatFrequencyMS for
-      # this test. This setting ensures that the retried insert will fail
-      # after 5 seconds if the driver does not properly cancel the in progress
-      # check.
-      serverSelectionTimeoutMS: 5000
-      appname: cancelServerCheckTest
-    operations:
-      # Perform an operation to ensure the node is discovered.
-      - name: insertOne
-        object: collection
-        arguments:
-          document:
-            _id: 1
-      # Configure the next inserts to fail with a non-timeout network error.
-      # This should:
-      # 1) Mark the server Unknown
-      # 2) Clear the connection pool
-      # 3) Cancel the in progress hello or legacy hello check and close the Monitor
-      #    connection
-      # 4) The write will be then we retried, server selection will request an
-      #    immediate check, and block for ~500ms until the next Monitor check
-      #    proceeds.
-      # 5) The write will succeed on the second attempt.
-      - name: configureFailPoint
-        object: testRunner
-        arguments:
-          failPoint:
-            configureFailPoint: failCommand
-            mode: { times: 1 }
-            data:
-                failCommands: ["insert"]
-                closeConnection: True
-      - name: insertOne
-        object: collection
-        arguments:
-          document:
-            _id: 2
-        result:
-          insertedId: 2
-      # The first error should mark the server Unknown and then clear the pool.
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-      # Perform another operation to ensure the node still selectable.
-      - name: insertOne
-        object: collection
-        arguments:
-          document:
-            _id: 3
-        result:
-          insertedId: 3
-      # Assert the server was marked Unknown and pool was cleared exactly once.
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-
-    # Order of operations is non-deterministic so we cannot check events.
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 2}
-          - {_id: 3}

data/spec/spec_tests/data/sdam_integration/connectTimeoutMS.yml

@@ -1,88 +0,0 @@
-# Test SDAM error handling.
-runOn:
-    # failCommand appName requirements
-    - minServerVersion: "4.4"
-
-database_name: &database_name "sdam-tests"
-collection_name: &collection_name "connectTimeoutMS"
-
-data: []
-
-tests:
-  - description: connectTimeoutMS=0
-    clientOptions:
-      retryWrites: false
-      connectTimeoutMS: 0
-      heartbeatFrequencyMS: 500
-      appname: connectTimeoutMS=0
-    operations:
-      # Perform an operation to ensure the node is discovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 1
-            - _id: 2
-      # Block the next streaming hello check for longer than
-      # heartbeatFrequencyMS to ensure that the connection timeout remains
-      # unlimited.
-      - name: configureFailPoint
-        object: testRunner
-        arguments:
-          failPoint:
-            configureFailPoint: failCommand
-            mode: { times: 2 }
-            data:
-                failCommands: ["hello", "isMaster"]
-                appName: connectTimeoutMS=0
-                blockConnection: true
-                blockTimeMS: 550
-      - name: wait
-        object: testRunner
-        arguments:
-          ms: 750
-      # Perform an operation to ensure the node is still selectable.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 3
-            - _id: 4
-      # Assert that the server was never marked Unknown and the pool was never
-      # cleared.
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 0
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 0
-
-    expectations:
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 1
-              - _id: 2
-          command_name: insert
-          database_name: *database_name
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 3
-              - _id: 4
-          command_name: insert
-          database_name: *database_name
-
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 2}
-          - {_id: 3}
-          - {_id: 4}

data/spec/spec_tests/data/sdam_integration/find-network-error.yml

@@ -1,85 +0,0 @@
-# Test SDAM error handling.
-runOn:
-    # failCommand appName requirements
-    - minServerVersion: "4.4"
-      # TODO Remove the line below when load balancer is ready
-      topology: ["replicaset","sharded","single"]
-
-database_name: &database_name "sdam-tests"
-collection_name: &collection_name "find-network-error"
-
-data: &data
-  - {_id: 1}
-  - {_id: 2}
-
-tests:
-  - description: Reset server and pool after network error on find
-    failPoint:
-      configureFailPoint: failCommand
-      mode: { times: 1 }
-      data:
-          failCommands: ["find"]
-          closeConnection: true
-          appName: findNetworkErrorTest
-    clientOptions:
-      retryWrites: false
-      retryReads: false
-      appname: findNetworkErrorTest
-    operations:
-      - name: find
-        object: collection
-        arguments:
-          filter:
-            _id: 1
-        error: true
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-      # Perform another operation to ensure the node is rediscovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 5
-            - _id: 6
-      # Assert the server was marked Unknown and pool was cleared exactly once.
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-
-    expectations:
-      - command_started_event:
-          command:
-            find: *collection_name
-          command_name: find
-          database_name: *database_name
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 5
-              - _id: 6
-          command_name: insert
-          database_name: *database_name
-
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 2}
-          - {_id: 5}
-          - {_id: 6}

data/spec/spec_tests/data/sdam_integration/find-shutdown-error.yml

@@ -1,118 +0,0 @@
-# Test SDAM error handling.
-runOn:
-    # failCommand appName requirements
-    - minServerVersion: "4.4"
-      # TODO Remove the line below when load balancer is ready
-      topology: ["replicaset","sharded","single"]
-
-database_name: &database_name "sdam-tests"
-collection_name: &collection_name "find-shutdown-error"
-
-data: []
-
-tests:
-  - description: Concurrent shutdown error on find
-    clientOptions:
-      retryWrites: false
-      retryReads: false
-      heartbeatFrequencyMS: 500
-      appname: shutdownErrorFindTest
-    operations:
-      # Perform an operation to ensure the node is discovered.
-      - name: insertOne
-        object: collection
-        arguments:
-          document:
-            _id: 1
-      # Configure the next two finds to fail with a non-timeout shutdown
-      # errors. Block the connection for 500ms to ensure both operations check
-      # out connections from the same pool generation.
-      - name: configureFailPoint
-        object: testRunner
-        arguments:
-          failPoint:
-            configureFailPoint: failCommand
-            mode: { times: 2 }
-            data:
-                failCommands: ["find"]
-                appName: shutdownErrorFindTest
-                errorCode: 91
-                blockConnection: true
-                blockTimeMS: 500
-      # Start threads.
-      - name: startThread
-        object: testRunner
-        arguments:
-          name: thread1
-      - name: startThread
-        object: testRunner
-        arguments:
-          name: thread2
-      # Perform concurrent find operations. Both fail with shutdown errors.
-      - name: runOnThread
-        object: testRunner
-        arguments:
-          name: thread1
-          operation:
-            name: find
-            object: collection
-            arguments:
-              filter:
-                _id: 1
-            error: true
-      - name: runOnThread
-        object: testRunner
-        arguments:
-          name: thread2
-          operation:
-            name: find
-            object: collection
-            arguments:
-              filter:
-                _id: 1
-            error: true
-      # Stop threads.
-      - name: waitForThread
-        object: testRunner
-        arguments:
-          name: thread1
-      - name: waitForThread
-        object: testRunner
-        arguments:
-          name: thread2
-      # The first shutdown error should mark the server Unknown and then clear
-      # the pool.
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-      # Perform an operation to ensure the node is rediscovered.
-      - name: insertOne
-        object: collection
-        arguments:
-          document:
-            _id: 4
-      # Assert the server was marked Unknown and pool was cleared exactly once.
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: assertEventCount
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-
-    # Order of operations is non-deterministic so we cannot check events.
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 4}

data/spec/spec_tests/data/sdam_integration/hello-command-error.yml

@@ -1,152 +0,0 @@
-# Test SDAM error handling.
-runOn:
-    # failCommand appName requirements
-    - minServerVersion: "4.9"
-      # TODO Remove the line below when load balancer is completed.
-      topology: ["replicaset","sharded","single"]
-
-database_name: &database_name "sdam-tests"
-collection_name: &collection_name "hello-command-error"
-
-data: []
-
-tests:
-  - description: Command error on Monitor handshake
-    # Configure the initial handshake to fail with a command error.
-    # Use times: 2 so that the RTT hello fails as well.
-    failPoint:
-      configureFailPoint: failCommand
-      mode: { times: 2 }
-      data:
-          failCommands: ["hello", "isMaster"]
-          appName: commandErrorHandshakeTest
-          closeConnection: false
-          errorCode: 91 # ShutdownInProgress
-    clientOptions:
-      retryWrites: false
-      connectTimeoutMS: 250
-      heartbeatFrequencyMS: 500
-      appname: commandErrorHandshakeTest
-    operations:
-      # The command error on the initial handshake should mark the server
-      # Unknown (emitting a ServerDescriptionChangedEvent) and clear the pool.
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      # Perform an operation to ensure the node is discovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 1
-            - _id: 2
-      # We cannot assert the server was marked Unknown and pool was cleared an
-      # exact number of times because the RTT hello may or may not have
-      # triggered this failpoint as well.
-      # - name: assertEventCount
-      #   object: testRunner
-      #   arguments:
-      #     event: ServerMarkedUnknownEvent
-      #     count: 1
-      # - name: assertEventCount
-      #   object: testRunner
-      #   arguments:
-      #     event: PoolClearedEvent
-      #     count: 1
-
-    expectations:
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 1
-              - _id: 2
-          command_name: insert
-          database_name: *database_name
-
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 2}
-
-  - description: Command error on Monitor check
-    clientOptions:
-      retryWrites: false
-      connectTimeoutMS: 1000
-      heartbeatFrequencyMS: 500
-      appname: commandErrorCheckTest
-    operations:
-      # Perform an operation to ensure the node is discovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 1
-            - _id: 2
-      # Configure the next streaming hello check to fail with a command error.
-      # Must use "times: 2" here. For a longer on explanation on why, check out
-      # https://jira.mongodb.org/browse/RUBY-3050.
-      - name: configureFailPoint
-        object: testRunner
-        arguments:
-          failPoint:
-            configureFailPoint: failCommand
-            mode: { times: 2 }
-            data:
-                failCommands: ["hello", "isMaster"]
-                appName: commandErrorCheckTest
-                closeConnection: false
-                blockConnection: true
-                blockTimeMS: 750
-                errorCode: 91 # ShutdownInProgress
-      # The command error on the next check should mark the server Unknown and
-      # clear the pool.
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-      # Perform an operation to ensure the node is rediscovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 3
-            - _id: 4
-      # We cannot assert the server was marked Unknown and pool was cleared an
-      # exact number of times because the RTT hello may have triggered this
-      # failpoint one or many times as well.
-
-    expectations:
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 1
-              - _id: 2
-          command_name: insert
-          database_name: *database_name
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 3
-              - _id: 4
-          command_name: insert
-          database_name: *database_name
-
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 2}
-          - {_id: 3}
-          - {_id: 4}

data/spec/spec_tests/data/sdam_integration/hello-network-error.yml

@@ -1,148 +0,0 @@
-#hello Test SDAM error handling.
-runOn:
-    # failCommand appName requirements
-    - minServerVersion: "4.9"
-      # TODO Uncomment the line below when load balancer is ready.
-      topology: ["replicaset","sharded","single"]
-
-database_name: &database_name "sdam-tests"
-collection_name: &collection_name "hello-network-error"
-
-data: []
-
-tests:
-  - description: Network error on Monitor handshake
-    # Configure the initial handshake to fail with a network error.
-    # Use times: 2 so that the RTT hello fails as well.
-    failPoint:
-      configureFailPoint: failCommand
-      mode: { times: 2 }
-      data:
-          failCommands: ["hello", "isMaster"]
-          appName: networkErrorHandshakeTest
-          closeConnection: true
-    clientOptions:
-      retryWrites: false
-      connectTimeoutMS: 250
-      heartbeatFrequencyMS: 500
-      appname: networkErrorHandshakeTest
-    operations:
-      # The network error on the initial handshake should mark the server
-      # Unknown (emitting a ServerDescriptionChangedEvent) and clear the pool.
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      # Perform an operation to ensure the node is discovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 1
-            - _id: 2
-      # We cannot assert the server was marked Unknown and pool was cleared an
-      # exact number of times because the RTT hello may or may not have
-      # triggered this failpoint as well.
-
-    expectations:
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 1
-              - _id: 2
-          command_name: insert
-          database_name: *database_name
-
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 2}
-
-  - description: Network error on Monitor check
-    clientOptions:
-      retryWrites: false
-      connectTimeoutMS: 250
-      heartbeatFrequencyMS: 500
-      appname: networkErrorCheckTest
-    operations:
-      # Perform an operation to ensure the node is discovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 1
-            - _id: 2
-      # Configure the next streaming hello check to fail with a non-timeout
-      # network error. Must use "times: 2" here. For a longer on explanation
-      # on why, check out https://jira.mongodb.org/browse/RUBY-3050.
-      - name: configureFailPoint
-        object: testRunner
-        arguments:
-          failPoint:
-            configureFailPoint: failCommand
-            mode: { times: 2 }
-            data:
-                failCommands: ["hello", "isMaster"]
-                appName: networkErrorCheckTest
-                closeConnection: true
-      # The network error on the next check should mark the server Unknown and
-      # clear the pool.
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: ServerMarkedUnknownEvent
-          count: 1
-      - name: waitForEvent
-        object: testRunner
-        arguments:
-          event: PoolClearedEvent
-          count: 1
-      # Perform an operation to ensure the node is rediscovered.
-      - name: insertMany
-        object: collection
-        arguments:
-          documents:
-            - _id: 3
-            - _id: 4
-      # We cannot assert the server was marked Unknown and pool was cleared an
-      # exact number of times because the RTT hello may have triggered this
-      # failpoint one or many times as well.
-      # - name: assertEventCount
-      #   object: testRunner
-      #   arguments:
-      #     event: ServerMarkedUnknownEvent
-      #     count: 1
-      # - name: assertEventCount
-      #   object: testRunner
-      #   arguments:
-      #     event: PoolClearedEvent
-      #     count: 1
-
-    expectations:
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 1
-              - _id: 2
-          command_name: insert
-          database_name: *database_name
-      - command_started_event:
-          command:
-            insert: *collection_name
-            documents:
-              - _id: 3
-              - _id: 4
-          command_name: insert
-          database_name: *database_name
-
-    outcome:
-      collection:
-        data:
-          - {_id: 1}
-          - {_id: 2}
-          - {_id: 3}
-          - {_id: 4}