Skip to content

Commit 8217627

Browse files
Merge pull request #230251 from ealsur/users/ealsur/availabilitysession
Adding session details for multi master
2 parents c33f44c + b3b1fd1 commit 8217627

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/nosql/troubleshoot-sdk-availability.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Diagnose and troubleshoot the availability of Azure Cosmos DB SDKs in mul
33
description: Learn all about the Azure Cosmos DB SDK availability behavior when operating in multi regional environments.
44
author: ealsur
55
ms.service: cosmos-db
6-
ms.date: 09/27/2022
6+
ms.date: 03/10/2023
77
ms.author: maquaran
88
ms.subservice: nosql
99
ms.custom: ignite-2022
@@ -86,7 +86,7 @@ If the account is single write region and the regional outage occurs during a wr
8686

8787
## Session consistency guarantees
8888

89-
When using [session consistency](../consistency-levels.md#guarantees-associated-with-consistency-levels), the client needs to guarantee that it can read its own writes. In single write region accounts where the read region preference is different from the write region, there could be cases where the user issues a write and when doing a read from a local region, the local region hasn't yet received the data replication (speed of light constraint). In such cases, the SDK detects the specific failure on the read operation and retries the read on the primary region to ensure session consistency.
89+
When using [session consistency](../consistency-levels.md#guarantees-associated-with-consistency-levels), the client needs to guarantee that it can read its own writes. In single write region accounts where the read region preference is different from the write region, there could be cases where the user issues a write and then does a read from a local region, the local region hasn't yet received the data replication (speed of light constraint). In such cases, the SDK receives a specific failure from the service on the read operation and retries the read on the primary region to ensure session consistency. For accounts with multiple write regions, the same session semantics apply but because there are multiple write regions available, retries are issued using the preferred region list or account's region order.
9090

9191
## Transient connectivity issues on TCP protocol
9292

0 commit comments

Comments
 (0)