...

Text file src/go.mongodb.org/mongo-driver/testdata/connection-monitoring-and-pooling/pool-clear-schedule-run-interruptInUseConnections-false.yml

Documentation: go.mongodb.org/mongo-driver/testdata/connection-monitoring-and-pooling

     1version: 1
     2style: unit
     3description: Pool clear SHOULD schedule the next background thread run immediately (interruptInUseConnections = false)
     4poolOptions:
     5  # ensure it's not involved by default
     6  backgroundThreadIntervalMS: 10000
     7operations:
     8  - name: ready
     9  - name: checkOut
    10  - name: checkOut
    11    label: conn
    12  - name: checkIn
    13    connection: conn
    14  - name: clear
    15    interruptInUseConnections: false
    16  - name: waitForEvent
    17    event: ConnectionPoolCleared
    18    count: 1
    19    timeout: 1000
    20  - name: waitForEvent
    21    event: ConnectionClosed
    22    count: 1
    23    timeout: 1000
    24  - name: close
    25events:
    26  - type: ConnectionCheckedOut
    27    connectionId: 1
    28    address: 42
    29  - type: ConnectionCheckedOut
    30    connectionId: 2
    31    address: 42
    32  - type: ConnectionCheckedIn
    33    connectionId: 2
    34    address: 42
    35  - type: ConnectionPoolCleared
    36    interruptInUseConnections: false
    37  - type: ConnectionClosed
    38    connectionId: 2
    39    reason: stale
    40    address: 42
    41  - type: ConnectionPoolClosed
    42    address: 42
    43ignore:
    44  - ConnectionCreated
    45  - ConnectionPoolReady
    46  - ConnectionReady
    47  - ConnectionCheckOutStarted
    48  - ConnectionPoolCreated

View as plain text