mongo 2.21.0 → 2.21.2

data/spec/spec_tests/data/cmap/pool-checkout-error-closed.yml

@@ -1,38 +0,0 @@
-version: 1
-style: unit
-description: must throw error if checkOut is called on a closed pool
-operations:
-  - name: ready
-  - name: checkOut
-    label: conn1
-  - name: checkIn
-    connection: conn1
-  - name: close
-  - name: checkOut
-error:
-  type: PoolClosedError
-  message: Attempted to check out a connection from closed connection pool
-events:
-  - type: ConnectionPoolCreated
-    address: 42
-    options: 42
-  - type: ConnectionCheckOutStarted
-    address: 42
-  - type: ConnectionCheckedOut
-    address: 42
-    connectionId: 42
-  - type: ConnectionCheckedIn
-    address: 42
-    connectionId: 42
-  - type: ConnectionPoolClosed
-    address: 42
-  - type: ConnectionCheckOutStarted
-    address: 42
-  - type: ConnectionCheckOutFailed
-    address: 42
-    reason: poolClosed
-ignore:
-  - ConnectionPoolReady
-  - ConnectionCreated
-  - ConnectionReady
-  - ConnectionClosed

data/spec/spec_tests/data/cmap/pool-checkout-maxConnecting-is-enforced.yml

@@ -1,81 +0,0 @@
-version: 1
-style: integration
-description: maxConnecting is enforced
-# Remove the topology runOn requirement when cmap specs are adjusted for lbs
-runOn:
-  -
-    # required for blockConnection in fail point
-    minServerVersion: "4.4.0"
-  - topology: [ "single", "replicaset", "sharded" ]
-failPoint:
-  configureFailPoint: failCommand
-  # high amount to ensure not interfered with by monitor checks.
-  mode: { times: 50 }
-  data:
-    failCommands: ["isMaster","hello"]
-    closeConnection: false
-    blockConnection: true
-    blockTimeMS: 750
-poolOptions:
-  maxPoolSize: 10
-  waitQueueTimeoutMS: 5000
-operations:
-  - name: ready
-  # start 3 threads
-  - name: start
-    target: thread1
-  - name: start
-    target: thread2
-  - name: start
-    target: thread3
-  # start creating a Connection. This will take a while
-  # due to the fail point.
-  - name: checkOut
-    thread: thread1
-  # wait for thread1 to actually start creating a Connection
-  - name: waitForEvent
-    event: ConnectionCreated
-    count: 1
-  # wait some more time to ensure thread1 has begun establishing a Connection
-  - name: wait
-    ms: 100
-  # start 2 check out requests. Only one thread should
-  # start creating a Connection and the other one should be
-  # waiting for pendingConnectionCount to be less than maxConnecting,
-  # only starting once thread1 finishes creating its Connection.
-  - name: checkOut
-    thread: thread2
-  - name: checkOut
-    thread: thread3
-  # wait until all Connections have been created.
-  - name: waitForEvent
-    event: ConnectionReady
-    count: 3
-events:
-  # thread1 creates its connection
-  - type: ConnectionCreated
-    address: 42
-    connectionId: 1
-  # either thread2 or thread3 creates its connection
-  # the other thread is stuck waiting for maxConnecting to come down
-  - type: ConnectionCreated
-    address: 42
-  # thread1 finishes establishing its connection, freeing
-  # up the blocked thread to start establishing
-  - type: ConnectionReady
-    address: 42
-    connectionId: 1
-  - type: ConnectionCreated
-    address: 42
-  # the remaining two Connections finish establishing
-  - type: ConnectionReady
-    address: 42
-  - type: ConnectionReady
-    address: 42
-ignore:
-  - ConnectionCheckOutStarted
-  - ConnectionCheckedIn
-  - ConnectionCheckedOut
-  - ConnectionClosed
-  - ConnectionPoolCreated
-  - ConnectionPoolReady

data/spec/spec_tests/data/cmap/pool-checkout-maxConnecting-timeout.yml

@@ -1,71 +0,0 @@
-version: 1
-style: integration
-description: waiting on maxConnecting is limited by WaitQueueTimeoutMS
-# Remove the topology runOn requirement when cmap specs are adjusted for lbs
-runOn:
-  -
-    # required for blockConnection in fail point
-    minServerVersion: "4.4.0"
-  - topology: [ "single", "replicaset", "sharded" ]
-failPoint:
-  configureFailPoint: failCommand
-  # high amount to ensure not interfered with by monitor checks.
-  mode: { times: 50 }
-  data:
-    failCommands: ["isMaster","hello"]
-    closeConnection: false
-    blockConnection: true
-    blockTimeMS: 750
-poolOptions:
-  maxPoolSize: 10
-  # Drivers that limit connection establishment by waitQueueTimeoutMS may skip
-  # this test. While waitQueueTimeoutMS is technically not supposed to limit establishment time,
-  # it will soon be deprecated, so it is easier for those drivers to just skip this test.
-  waitQueueTimeoutMS: 50
-operations:
-  - name: ready
-  # start creating two connections simultaneously.
-  - name: start
-    target: thread1
-  - name: checkOut
-    thread: thread1
-  - name: start
-    target: thread2
-  - name: checkOut
-    thread: thread2
-  # wait for other two threads to start establishing
-  - name: waitForEvent
-    event: ConnectionCreated
-    count: 2
-  # start a third thread that will be blocked waiting for
-  # one of the other two to finish
-  - name: start
-    target: thread3
-  - name: checkOut
-    thread: thread3
-  - name: waitForEvent
-    event: ConnectionCheckOutFailed
-    count: 1
-  # rejoin thread3, should experience error
-  - name: waitForThread
-    target: thread3
-error:
-  type: WaitQueueTimeoutError
-  message: Timed out while checking out a connection from connection pool
-events:
-  - type: ConnectionCheckOutStarted
-    address: 42
-  - type: ConnectionCheckOutStarted
-    address: 42
-  - type: ConnectionCheckOutStarted
-    address: 42
-  - type: ConnectionCheckOutFailed
-    reason: timeout
-    address: 42
-ignore:
-  - ConnectionCreated
-  - ConnectionCheckedIn
-  - ConnectionCheckedOut
-  - ConnectionClosed
-  - ConnectionPoolCreated
-  - ConnectionPoolReady

data/spec/spec_tests/data/cmap/pool-checkout-minPoolSize-connection-maxConnecting.yml

@@ -1,64 +0,0 @@
-version: 1
-style: integration
-description: threads blocked by maxConnecting check out minPoolSize connections
-runOn:
-  -
-    # required for blockConnection in fail point
-    minServerVersion: "4.4.0"
-  - topology: [ "single", "replicaset", "sharded" ]
-failPoint:
-  configureFailPoint: failCommand
-  mode: "alwaysOn"
-  data:
-    failCommands: ["isMaster","hello"]
-    closeConnection: false
-    blockConnection: true
-    blockTimeMS: 1000
-poolOptions:
-  # allows both thread1 and the background thread to start opening connections concurrently
-  minPoolSize: 2
-  # gives opportunity for the checkout in thread2 to open a new connection, which it must not do nonetheless
-  maxPoolSize: 3
-  waitQueueTimeoutMS: 5000
-operations:
-  - name: ready
-  # thread1 exists to hold on one of the two permits to open a connection (the other one is initially held by the background thread),
-  # so that thread2 would be blocked acquiring a permit, which opens an opportunity for it to grab the connection newly opened
-  # by the background thread instead of opening a third connection.
-  - name: start
-    target: thread1
-  - name: start
-    target: thread2
-  # Ideally, thread1 should be holding for its permit to open a connection till the end of the test, but we cannot express that.
-  # This delay emulates the above requirement:
-  # - it is long enough to make sure that the background thread opens a connection before thread1 releases its permit;
-  # - it is short enough to allow thread2 to become blocked acquiring a permit to open a connection, and then grab the connection
-  #   opened by the background thread, before the background thread releases its permit.
-  - name: wait
-    ms: 200
-  - name: checkOut
-    thread: thread1
-  - name: waitForEvent
-    event: ConnectionCreated
-    count: 2
-  - name: checkOut
-    thread: thread2
-  - name: waitForEvent
-    event: ConnectionCheckedOut
-    count: 2
-events:
-  # exactly 2 connections must be created and checked out
-  - type: ConnectionCreated
-    address: 42
-  - type: ConnectionCreated
-    address: 42
-  - type: ConnectionCheckedOut
-    address: 42
-  - type: ConnectionCheckedOut
-    address: 42
-ignore:
-  - ConnectionPoolReady
-  - ConnectionClosed
-  - ConnectionReady
-  - ConnectionPoolCreated
-  - ConnectionCheckOutStarted

data/spec/spec_tests/data/cmap/pool-checkout-multiple.yml

@@ -1,39 +0,0 @@
-version: 1
-style: unit
-description: must be able to check out multiple connections at the same time
-operations:
-  - name: ready
-  - name: start
-    target: thread1
-  - name: start
-    target: thread2
-  - name: start
-    target: thread3
-  - name: checkOut
-    thread: thread1
-  - name: checkOut
-    thread: thread2
-  - name: checkOut
-    thread: thread3
-  - name: waitForThread
-    target: thread1
-  - name: waitForThread
-    target: thread2
-  - name: waitForThread
-    target: thread3
-events:
-  - type: ConnectionCheckedOut
-    connectionId: 42
-    address: 42
-  - type: ConnectionCheckedOut
-    connectionId: 42
-    address: 42
-  - type: ConnectionCheckedOut
-    connectionId: 42
-    address: 42
-ignore:
-  - ConnectionCreated
-  - ConnectionPoolReady
-  - ConnectionReady
-  - ConnectionPoolCreated
-  - ConnectionCheckOutStarted

data/spec/spec_tests/data/cmap/pool-checkout-no-idle.yml

@@ -1,41 +0,0 @@
-version: 1
-style: unit
-description: must destroy and must not check out an idle connection if found while iterating available connections
-poolOptions:
-  maxIdleTimeMS: 10
-  backgroundThreadIntervalMS: -1
-operations:
-  - name: ready
-  - name: checkOut
-    label: conn
-  - name: checkIn
-    connection: conn
-  - name: wait
-    ms: 50
-  - name: checkOut
-  - name: waitForEvent
-    event: ConnectionCheckedOut
-    count: 2
-events:
-  - type: ConnectionPoolCreated
-    address: 42
-    options: 42
-  - type: ConnectionCheckedOut
-    connectionId: 1
-    address: 42
-  - type: ConnectionCheckedIn
-    connectionId: 1
-    address: 42
-  # In between these, wait so connection becomes idle
-  - type: ConnectionClosed
-    connectionId: 1
-    reason: idle
-    address: 42
-  - type: ConnectionCheckedOut
-    connectionId: 2
-    address: 42
-ignore:
-  - ConnectionReady
-  - ConnectionPoolReady
-  - ConnectionCreated
-  - ConnectionCheckOutStarted

data/spec/spec_tests/data/cmap/pool-checkout-no-stale.yml

@@ -1,41 +0,0 @@
-version: 1
-style: unit
-description: must destroy and must not check out a stale connection if found while iterating available connections
-poolOptions:
-  backgroundThreadIntervalMS: -1
-operations:
-  - name: ready
-  - name: checkOut
-    label: conn
-  - name: checkIn
-    connection: conn
-  - name: clear
-  - name: ready
-  - name: checkOut
-  - name: waitForEvent
-    event: ConnectionCheckedOut
-    count: 2
-events:
-  - type: ConnectionPoolCreated
-    address: 42
-    options: 42
-  - type: ConnectionCheckedOut
-    connectionId: 1
-    address: 42
-  - type: ConnectionCheckedIn
-    connectionId: 1
-    address: 42
-  - type: ConnectionPoolCleared
-    address: 42
-  - type: ConnectionClosed
-    connectionId: 1
-    reason: stale
-    address: 42
-  - type: ConnectionCheckedOut
-    connectionId: 2
-    address: 42
-ignore:
-  - ConnectionReady
-  - ConnectionPoolReady
-  - ConnectionCreated
-  - ConnectionCheckOutStarted

data/spec/spec_tests/data/cmap/pool-checkout-returned-connection-maxConnecting.yml

@@ -1,88 +0,0 @@
-version: 1
-style: integration
-description: threads blocked by maxConnecting check out returned connections
-# Remove the topology runOn requirement when cmap specs are adjusted for lbs
-runOn:
-  -
-    # required for blockConnection in fail point
-    minServerVersion: "4.4.0"
-  - topology: [ "single", "replicaset", "sharded" ]
-failPoint:
-  configureFailPoint: failCommand
-  # high amount to ensure not interfered with by monitor checks.
-  mode: { times: 50 }
-  data:
-    failCommands: ["isMaster","hello"]
-    closeConnection: false
-    blockConnection: true
-    blockTimeMS: 750
-poolOptions:
-  maxPoolSize: 10
-  waitQueueTimeoutMS: 5000
-operations:
-  - name: ready
-  # check out a connection and hold on to it.
-  - name: checkOut
-    label: conn0
-  # then start three threads that all attempt to check out. Two threads
-  # will fill maxConnecting, and the other should be waiting either for
-  # the other two to finish or for the main thread to check its connection
-  # back in.
-  - name: start
-    target: thread1
-  - name: checkOut
-    thread: thread1
-  - name: start
-    target: thread2
-  - name: checkOut
-    thread: thread2
-  - name: start
-    target: thread3
-  - name: checkOut
-    thread: thread3
-  # wait for all three to start checking out and a little longer
-  # for the establishments to begin.
-  - name: waitForEvent
-    event: ConnectionCheckOutStarted
-    count: 4
-  - name: wait
-    ms: 100
-  # check original connection back in, so the thread that isn't
-  # currently establishing will become unblocked. Then wait for
-  # all threads to complete.
-  - name: checkIn
-    connection: conn0
-  - name: waitForEvent
-    event: ConnectionCheckedOut
-    count: 4
-events:
-  # main thread checking out a Connection and holding it
-  - type: ConnectionCreated
-    address: 42
-    connectionId: 1
-  - type: ConnectionCheckedOut
-    address: 42
-  # two threads creating their Connections
-  - type: ConnectionCreated
-    address: 42
-  - type: ConnectionCreated
-    address: 42
-  # main thread checking its Connection back in
-  - type: ConnectionCheckedIn
-    connectionId: 1
-    address: 42
-  # remaining thread checking out the returned Connection
-  - type: ConnectionCheckedOut
-    connectionId: 1
-    address: 42
-  # first two threads finishing Connection establishment
-  - type: ConnectionCheckedOut
-    address: 42
-  - type: ConnectionCheckedOut
-    address: 42
-ignore:
-  - ConnectionPoolReady
-  - ConnectionClosed
-  - ConnectionReady
-  - ConnectionPoolCreated
-  - ConnectionCheckOutStarted

data/spec/spec_tests/data/cmap/pool-clear-interrupting-pending-connections.yml

@@ -1,43 +0,0 @@
-version: 1
-style: integration
-description: clear with interruptInUseConnections = true closes pending connections
-# Remove the topology runOn requirement when cmap specs are adjusted for lbs
-runOn:
-  - minServerVersion: "4.9.0"
-  - topology: [ "single", "replicaset", "sharded" ]
-failPoint:
-  configureFailPoint: failCommand
-  mode: "alwaysOn"
-  data:
-    failCommands: ["isMaster","hello"]
-    closeConnection: false
-    blockConnection: true
-    blockTimeMS: 1000
-poolOptions:
-  minPoolSize: 0
-operations:
-  - name: ready
-  - name: start
-    target: thread1
-  - name: checkOut
-    thread: thread1
-  - name: waitForEvent
-    event: ConnectionCreated
-    count: 1
-  - name: clear
-    interruptInUseConnections: true
-  - name: waitForEvent
-    event: ConnectionCheckOutFailed
-    count: 1
-events:
-  - type: ConnectionCheckOutStarted
-  - type: ConnectionCreated
-  - type: ConnectionPoolCleared
-    interruptInUseConnections: true
-  - type: ConnectionClosed
-  - type: ConnectionCheckOutFailed
-ignore:
-  - ConnectionCheckedIn
-  - ConnectionCheckedOut
-  - ConnectionPoolCreated
-  - ConnectionPoolReady

data/spec/spec_tests/data/cmap/pool-clear-min-size.yml

@@ -1,41 +0,0 @@
-version: 1
-style: unit
-description: pool clear halts background minPoolSize establishments
-poolOptions:
-  minPoolSize: 1
-  backgroundThreadIntervalMS: 50
-# Remove this runOn requirement when cmap specs are adjusted for lbs
-runOn:
-  -
-    topology: [ "single", "replicaset", "sharded" ]
-operations:
-  - name: ready
-  - name: waitForEvent
-    event: ConnectionReady
-    count: 1
-  - name: clear
-  # ensure no connections created after clear
-  - name: wait
-    ms: 200
-  - name: ready
-  - name: waitForEvent
-    event: ConnectionReady
-    count: 2
-events:
-  - type: ConnectionPoolReady
-    address: 42
-  - type: ConnectionCreated
-    address: 42
-  - type: ConnectionReady
-    address: 42
-  - type: ConnectionPoolCleared
-    address: 42
-  - type: ConnectionPoolReady
-    address: 42
-  - type: ConnectionCreated
-    address: 42
-  - type: ConnectionReady
-    address: 42
-ignore:
-  - ConnectionPoolCreated
-  - ConnectionClosed

data/spec/spec_tests/data/cmap/pool-clear-paused.yml

@@ -1,18 +0,0 @@
-version: 1
-style: unit
-description: clearing a paused pool emits no events
-# Remove the topology runOn requirement when cmap specs are adjusted for lbs
-runOn:
-  - topology: [ "single", "replicaset", "sharded" ]
-operations:
-  - name: clear
-  - name: ready
-  - name: clear
-  - name: clear
-events:
-  - type: ConnectionPoolReady
-    address: 42
-  - type: ConnectionPoolCleared
-    address: 42
-ignore:
-  - ConnectionPoolCreated

data/spec/spec_tests/data/cmap/pool-clear-ready.yml

@@ -1,39 +0,0 @@
-version: 1
-style: unit
-description: after clear, cannot check out connections until pool ready
-# Remove the topology runOn requirement when cmap specs are adjusted for lbs
-runOn:
-  - topology: [ "single", "replicaset", "sharded" ]
-operations:
-  - name: ready
-  - name: checkOut
-  - name: clear
-  - name: start
-    target: thread1
-  - name: checkOut
-    thread: thread1
-  - name: waitForEvent
-    event: ConnectionCheckOutFailed
-    count: 1
-  - name: ready
-  - name: checkOut
-events:
-  - type: ConnectionPoolReady
-    address: 42
-  - type: ConnectionCheckedOut
-    address: 42
-    connectionId: 42
-  - type: ConnectionPoolCleared
-    address: 42
-  - type: ConnectionCheckOutFailed
-    address: 42
-    reason: connectionError
-  - type: ConnectionPoolReady
-    address: 42
-  - type: ConnectionCheckedOut
-    address: 42
-ignore:
-  - ConnectionPoolCreated
-  - ConnectionReady
-  - ConnectionCheckOutStarted
-  - ConnectionCreated

data/spec/spec_tests/data/cmap/pool-clear-schedule-run-interruptInUseConnections-false.yml

@@ -1,48 +0,0 @@
-version: 1
-style: unit
-description: Pool clear SHOULD schedule the next background thread run immediately (interruptInUseConnections = false)
-poolOptions:
-  # ensure it's not involved by default
-  backgroundThreadIntervalMS: 10000
-operations:
-  - name: ready
-  - name: checkOut
-  - name: checkOut
-    label: conn
-  - name: checkIn
-    connection: conn
-  - name: clear
-    interruptInUseConnections: false
-  - name: waitForEvent
-    event: ConnectionPoolCleared
-    count: 1
-    timeout: 1000
-  - name: waitForEvent
-    event: ConnectionClosed
-    count: 1
-    timeout: 1000
-  - name: close
-events:
-  - type: ConnectionCheckedOut
-    connectionId: 1
-    address: 42
-  - type: ConnectionCheckedOut
-    connectionId: 2
-    address: 42
-  - type: ConnectionCheckedIn
-    connectionId: 2
-    address: 42
-  - type: ConnectionPoolCleared
-    interruptInUseConnections: false
-  - type: ConnectionClosed
-    connectionId: 2
-    reason: stale
-    address: 42
-  - type: ConnectionPoolClosed
-    address: 42
-ignore:
-  - ConnectionCreated
-  - ConnectionPoolReady
-  - ConnectionReady
-  - ConnectionCheckOutStarted
-  - ConnectionPoolCreated

data/spec/spec_tests/data/cmap/pool-close-destroy-conns.yml

@@ -1,30 +0,0 @@
-version: 1
-style: unit
-description: When a pool is closed, it MUST first destroy all available connections in that pool
-operations:
-  - name: ready
-  - name: checkOut
-  - name: checkOut
-    label: conn
-  - name: checkOut
-  - name: checkIn
-    connection: conn
-  - name: close
-events:
-  - type: ConnectionCheckedIn
-    connectionId: 2
-    address: 42
-  - type: ConnectionClosed
-    connectionId: 2
-    reason: poolClosed
-    address: 42
-  - type: ConnectionPoolClosed
-    address: 42
-ignore:
-  - ConnectionCreated
-  - ConnectionPoolReady
-  - ConnectionReady
-  - ConnectionPoolCreated
-  - ConnectionCheckOutStarted
-  - ConnectionCheckedOut
-        

data/spec/spec_tests/data/cmap/pool-close.yml

@@ -1,11 +0,0 @@
-version: 1
-style: unit
-description: must be able to manually close a pool
-operations:
-  - name: close
-events:
-  - type: ConnectionPoolCreated
-    address: 42
-    options: 42
-  - type: ConnectionPoolClosed
-    address: 42