You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/api.rst
+56-3Lines changed: 56 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,6 +160,8 @@ Driver Configuration
160
160
Additional configuration can be provided via the :class:`neo4j.Driver` constructor.
161
161
162
162
163
+
+ :ref:`session-connection-timeout-ref`
164
+
+ :ref:`update-routing-table-timeout-ref`
163
165
+ :ref:`connection-acquisition-timeout-ref`
164
166
+ :ref:`connection-timeout-ref`
165
167
+ :ref:`encrypted-ref`
@@ -172,12 +174,59 @@ Additional configuration can be provided via the :class:`neo4j.Driver` construct
172
174
+ :ref:`user-agent-ref`
173
175
174
176
177
+
.. _session-connection-timeout-ref:
178
+
179
+
``session_connection_timeout``
180
+
------------------------------
181
+
The maximum amount of time in seconds the session will wait when trying to
182
+
establish a usable read/write connection to the remote host.
183
+
This encompasses *everything* that needs to happen for this, including,
184
+
if necessary, updating the routing table, fetching a connection from the pool,
185
+
and, if necessary fully establishing a new connection with the reader/writer.
186
+
187
+
Since this process may involve updating the routing table, acquiring a
188
+
connection from the pool, or establishing a new connection, it should be chosen
189
+
larger than :ref:`update-routing-table-timeout-ref`,
190
+
:ref:`connection-acquisition-timeout-ref`, and :ref:`connection-timeout-ref`.
191
+
192
+
:Type: ``float``
193
+
:Default: ``float("inf")``
194
+
195
+
.. versionadded:: 4.4.5
196
+
197
+
198
+
.. _update-routing-table-timeout-ref:
199
+
200
+
``update_routing_table_timeout``
201
+
--------------------------------
202
+
The maximum amount of time in seconds the driver will attempt to fetch a new
203
+
routing table. This encompasses *everything* that needs to happen for this,
204
+
including fetching connections from the pool, performing handshakes, and
205
+
requesting and receiving a fresh routing table.
206
+
207
+
Since this process may involve acquiring a connection from the pool, or
208
+
establishing a new connection, it should be chosen larger than
209
+
:ref:`connection-acquisition-timeout-ref` and :ref:`connection-timeout-ref`.
210
+
211
+
This setting only has an effect for :ref:`neo4j-driver-ref`, but not for
212
+
:ref:`bolt-driver-ref` as it does no routing at all.
213
+
214
+
:Type: ``float``
215
+
:Default: ``90.0``
216
+
217
+
.. versionadded:: 4.4.5
218
+
219
+
175
220
.. _connection-acquisition-timeout-ref:
176
221
177
222
``connection_acquisition_timeout``
178
223
----------------------------------
179
-
The maximum amount of time in seconds a session will wait when requesting a connection from the connection pool.
180
-
Since the process of acquiring a connection may involve creating a new connection, ensure that the value of this configuration is higher than the configured :ref:`connection-timeout-ref`.
224
+
The maximum amount of time in seconds the driver will wait to either acquire an
225
+
idle connection from the pool (including potential liveness checks) or create a
226
+
new connection when the pool is not full and all existing connection are in use.
227
+
228
+
Since this process may involve opening a new connection including handshakes,
229
+
it should be chosen larger than :ref:`connection-timeout-ref`.
181
230
182
231
:Type: ``float``
183
232
:Default: ``60.0``
@@ -187,7 +236,11 @@ Since the process of acquiring a connection may involve creating a new connectio
187
236
188
237
``connection_timeout``
189
238
----------------------
190
-
The maximum amount of time in seconds to wait for a TCP connection to be established.
239
+
The maximum amount of time in seconds to wait for a TCP connection to be
240
+
established.
241
+
242
+
This *does not* include any handshake(s), or authentication required before the
243
+
connection can be used to perform database related work.
0 commit comments