From 1376092896ad40db2e6374d44287add2a0171381 Mon Sep 17 00:00:00 2001 From: Valentin Kovalenko Date: Wed, 9 Aug 2023 11:30:58 -0600 Subject: [PATCH] Fix `ConnectionReadyEvent.duration`, take into account that this event is emitted not only when checking out DRIVERS-2469 --- .../connection-monitoring-and-pooling.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst b/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst index edaa73a099..3c63071e89 100644 --- a/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst +++ b/source/connection-monitoring-and-pooling/connection-monitoring-and-pooling.rst @@ -921,7 +921,8 @@ See the `Load Balancer Specification <../load-balancers/load-balancers.rst#event * it is the time elapsed between the `ConnectionCreatedEvent` * emitted by the same checking out and this event. * - * Naturally, this duration is not greater than + * Naturally, when establishing a connection is part of checking out, + * this duration is not greater than * `ConnectionCheckedOutEvent`/`ConnectionCheckOutFailedEvent.duration`. * * A driver that delivers events synchronously MUST NOT include in this duration