Skip to content

Commit bb8cae3

Browse files
author
Jake Willey
committed
Fix sdk version
1 parent 1f4427d commit bb8cae3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/sql/troubleshoot-dot-net-sdk-request-header-too-large.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to diagnose and fix the request header too large exceptio
44
author: j82w
55
ms.service: cosmos-db
66
ms.subservice: cosmosdb-sql
7-
ms.date: 07/13/2020
7+
ms.date: 09/29/2021
88
ms.author: jawilley
99
ms.topic: troubleshooting
1010
ms.reviewer: sngun
@@ -32,7 +32,7 @@ Restart your client application to reset all the session tokens. Eventually, the
3232

3333
#### Solution:
3434
> [!IMPORTANT]
35-
> Upgrade to at least .NET [v3.20.1](https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/changelog.md) or [v2.15.0](https://github.com/Azure/azure-cosmos-dotnet-v2/blob/master/changelog.md). These minor versions contain optimizations to reduce the session token size to prevent the header from growing and hitting the size limit.
35+
> Upgrade to at least .NET [v3.20.1](https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/changelog.md) or [v2.16.1](https://github.com/Azure/azure-cosmos-dotnet-v2/blob/master/changelog.md). These minor versions contain optimizations to reduce the session token size to prevent the header from growing and hitting the size limit.
3636
1. Follow the guidance in the [.NET v3](performance-tips-dotnet-sdk-v3-sql.md) or [.NET v2](performance-tips.md) performance tips articles. Convert the application to use the direct connection mode with the Transmission Control Protocol (TCP). The direct connection mode with the TCP protocol doesn't have the header size restriction like the HTTP protocol, so it avoids this issue. Make sure to use the latest version of the SDK, which has a fix for query operations when the service interop isn't available.
3737
1. If the direct connection mode with the TCP protocol isn't an option for your workload, mitigate it by changing the [client consistency level](how-to-manage-consistency.md). The session token is only used for session consistency, which is the default consistency level for Azure Cosmos DB. Other consistency levels don't use the session token.
3838

0 commit comments

Comments
 (0)