Skip to content

Commit 698f768

Browse files
Merge pull request #235802 from kushagraThapar/update_network_request_timeout_min_value
Updated min value of network request timeout to 1 second
2 parents 010e6e4 + 547d9c3 commit 698f768

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/nosql/tune-connection-configurations-java-sdk-v4.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ As a first step, use the following recommended configuration settings below. The
6969
| maxConnectionsPerEndpoint | "130" | "130" | This represents the upper bound size of the *connection pool* for an endpoint/backend node (representing a replica). SDK creates connections to endpoint/backend node on-demand and based on incoming concurrent requests. By default, if required, SDK will create maximum 130 connections to an endpoint/backend node. (NOTE: SDK doesn't create these 130 connections upfront). |
7070
| maxRequestsPerConnection | "30" | "30" | This represents the upper bound size of the maximum number of requests that can be queued on a *single connection* for a specific endpoint/backend node (representing a replica). SDK queues requests to a single connection to an endpoint/backend node on-demand and based on incoming concurrent requests. By default, if required, SDK will queue maximum 30 requests to a single connection for a specific endpoint/backend node. (NOTE: SDK doesn't queue these 30 requests to a single connection upfront). |
7171
| connectTimeout | "PT5S" | "~PT1S" | This represents the connection establishment timeout duration for a *single connection* to be established with an endpoint/backend node. By default SDK will wait for maximum 5 seconds for connection establishment before throwing an error. TCP connection establishment uses [multi-step handshake](https://en.wikipedia.org/wiki/Transmission_Control_Protocol#Protocol_operation) which increases latency of the connection establishment time, hence, customers are recommended to set this value according to their network bandwidth and environment settings. NOTE: This recommendation of ~PT1S is only for applications deployed in colocated regions of their Cosmos DB accounts. |
72-
| networkRequestTimeout | "PT5S" | "PT5S" | This represents the network timeout duration for a *single request*. SDK will wait maximum for this duration to consume a service response after the request has been written to the network connection. SDK only allows values between 5 seconds (min) and 10 seconds (max). Setting a value too high can result in fewer retries and reduce chances of success by retries. |
72+
| networkRequestTimeout | "PT5S" | "PT5S" | This represents the network timeout duration for a *single request*. SDK will wait maximum for this duration to consume a service response after the request has been written to the network connection. SDK only allows values between 1 second (min) and 10 seconds (max). Setting a value too high can result in fewer retries and reduce chances of success by retries. |
7373

7474

7575
### Gateway Connection mode

0 commit comments

Comments
 (0)