Cosmos Client Builder overrides direct connection config idleConnectionTimeout with gateway connection config

This is a bug which popped up in this ICM: https://portal.microsofticm.com/imp/v3/incidents/details/194516399/home

In the below code ->

if (this.directConnectionConfig != null) {

    this.connectionPolicy = new ConnectionPolicy(directConnectionConfig);

    //  Check if the user passed additional gateway connection configuration

    if (this.gatewayConnectionConfig != null) {

        this.connectionPolicy.setMaxConnectionPoolSize(this.gatewayConnectionConfig.getMaxConnectionPoolSize());

        this.connectionPolicy.setRequestTimeout(this.gatewayConnectionConfig.getRequestTimeout());


       //  gateway config overrides direct config right here
        this.connectionPolicy.setIdleConnectionTimeout(this.gatewayConnectionConfig.getIdleConnectionTimeout());

    }

If both directConnectionConfig and gatewayConnectionConfig are present, then idleConnectionTimeout will always be overriden by gatewayConnectionConfig

[allenhumphreys]

Excellent! Thanks @kushagraThapar

[moderakh]

our P99 latency for items of size 1KB is < 10ms however for some corner case scenario (query payload being huge, etc), the server side contract is to respond in 5 seconds, this is the reason the SDK default is 5 seconds.

I don’t think this will be hit on the normal path though. You can set it to 2 seconds provided that you are aware of the above.