Decrease the default 'TcpKeepAliveTime' for SDK3

Description

Currently the value for 'TcpKeepAliveTime' (as covered on https://docs.couchbase.com/dotnet-sdk/2.7/client-settings.html#dotnet-clientconfiguration-settings) is 2 hours.

This is a very long time and in some environments this is not a very sensible default; for example, for Azure all external connections have a tcp timeout of 4 minutes.
Clearly the .NET SDK connections will not start triggering the tcp keepalives before this timeout kicks in.

I guess the 2 hours was taken from the Windows default, but given that the interval we set TCP keep alives (after they start) is 1000ms, I think it would make sense to decrease the initial window to something much smaller, perhaps a minute or two at most?

Given this is a breaking change (as some people may have been relying on the old default) perhaps we can consider this for SDK 3?

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:

Jeffry Morris April 19, 2019 at 12:40 AM
Edited

Thanks - it might make sense to do this in a dot minor release for SDK 2.0; otherwise we can just improve the documentation for cloud based deployments since we know its an outstanding issue. As for 3.0, we can most definitly lower the values for SDK 3.0.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Components

Sprint

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created April 18, 2019 at 6:20 PM
Updated April 24, 2020 at 8:22 PM
Resolved September 11, 2019 at 4:25 AM
Instabug