mongo 2.12.4 → 2.14.0.rc1

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

@@ -0,0 +1,86 @@
+# Test SDAM error handling.
+runOn:
+    # failCommand appName requirements
+    - minServerVersion: "4.4"
+
+database_name: &database_name "sdam-tests"
+collection_name: &collection_name "insert-network-error"
+
+data: &data
+  - {_id: 1}
+  - {_id: 2}
+
+tests:
+  - description: Reset server and pool after network error on insert
+    failPoint:
+      configureFailPoint: failCommand
+      mode: { times: 1 }
+      data:
+          failCommands: ["insert"]
+          closeConnection: true
+          appName: insertNetworkErrorTest
+    clientOptions:
+      retryWrites: false
+      appname: insertNetworkErrorTest
+    operations:
+      - name: insertMany
+        object: collection
+        arguments:
+          documents:
+            - _id: 3
+            - _id: 4
+        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:
+            insert: *collection_name
+            documents:
+              - _id: 3
+              - _id: 4
+          command_name: insert
+          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/insert-shutdown-error.yml

@@ -0,0 +1,115 @@
+# Test SDAM error handling.
+runOn:
+    # failCommand appName requirements
+    - minServerVersion: "4.4"
+
+database_name: &database_name "sdam-tests"
+collection_name: &collection_name "insert-shutdown-error"
+
+data: []
+
+tests:
+  - description: Concurrent shutdown error on insert
+    clientOptions:
+      retryWrites: false
+      heartbeatFrequencyMS: 500
+      appname: shutdownErrorInsertTest
+    operations:
+      # Perform an operation to ensure the node is discovered.
+      - name: insertOne
+        object: collection
+        arguments:
+          document:
+            _id: 1
+      # Configure the next two inserts 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: ["insert"]
+                appName: shutdownErrorInsertTest
+                errorCode: 91
+                blockConnection: true
+                blockTimeMS: 500
+      # Start threads.
+      - name: startThread
+        object: testRunner
+        arguments:
+          name: thread1
+      - name: startThread
+        object: testRunner
+        arguments:
+          name: thread2
+      # Perform concurrent insert operations. Both fail with shutdown errors.
+      - name: runOnThread
+        object: testRunner
+        arguments:
+          name: thread1
+          operation:
+            name: insertOne
+            object: collection
+            arguments:
+              document:
+                _id: 2
+            error: true
+      - name: runOnThread
+        object: testRunner
+        arguments:
+          name: thread2
+          operation:
+            name: insertOne
+            object: collection
+            arguments:
+              document:
+                _id: 3
+            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/isMaster-command-error.yml

@@ -0,0 +1,168 @@
+# Test SDAM error handling.
+runOn:
+    # failCommand appName requirements
+    - minServerVersion: "4.4"
+
+database_name: &database_name "sdam-tests"
+collection_name: &collection_name "isMaster-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 isMaster fails as well.
+    failPoint:
+      configureFailPoint: failCommand
+      mode: { times: 2 }
+      data:
+          failCommands: ["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
+# https://jira.mongodb.org/browse/DRIVERS-1314
+#       - name: waitForEvent
+#         object: testRunner
+#         arguments:
+#           event: PoolClearedEvent
+#           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 isMaster 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 isMaster check to fail with a command
+      # error.
+      # Use times: 2 so that the RTT isMaster is blocked as well.
+      - name: configureFailPoint
+        object: testRunner
+        arguments:
+          failPoint:
+            configureFailPoint: failCommand
+            mode: { times: 2 }
+            data:
+                failCommands: ["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
+          # Ruby driver marks server unknown for each fail point hit
+          count: 2
+# Ruby driver normally produces 2 pool clears, but sometimes only 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
+      # Assert the server was marked Unknown and pool was cleared exactly once.
+      - name: assertEventCount
+        object: testRunner
+        arguments:
+          event: ServerMarkedUnknownEvent
+          # Ruby driver marks server unknown for each fail point hit
+          count: 2
+# Ruby driver normally produces 2 pool clears, but sometimes only 1
+#       - name: waitForEvent
+#         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}

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

@@ -0,0 +1,162 @@
+# Test SDAM error handling.
+runOn:
+    # failCommand appName requirements
+    - minServerVersion: "4.4"
+
+database_name: &database_name "sdam-tests"
+collection_name: &collection_name "isMaster-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 isMaster fails as well.
+    failPoint:
+      configureFailPoint: failCommand
+      mode: { times: 2 }
+      data:
+          failCommands: ["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
+# https://jira.mongodb.org/browse/DRIVERS-1314
+#       - name: waitForEvent
+#         object: testRunner
+#         arguments:
+#           event: PoolClearedEvent
+#           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 isMaster 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: 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 isMaster check to fail with a non-timeout
+      # network error. Use times: 2 to ensure that the the Monitor check fails
+      # since the RTT isMaster may trigger this failpoint as well.
+      - name: configureFailPoint
+        object: testRunner
+        arguments:
+          failPoint:
+            configureFailPoint: failCommand
+            mode: { times: 2 }
+            data:
+                failCommands: ["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 isMaster 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
+      - 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}