Skip to content

Commit 96141ed

Browse files
committed
rename
1 parent 8801c18 commit 96141ed

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/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 SDKs in multir
33
description: Learn all about the Azure Cosmos SDK availability behavior when operating in multi regional environments.
44
author: ealsur
55
ms.service: cosmos-db
6-
ms.date: 10/05/2020
6+
ms.date: 10/20/2020
77
ms.author: maquaran
88
ms.subservice: cosmosdb-sql
99
ms.topic: troubleshooting
@@ -70,7 +70,7 @@ If the account is single write region and the regional outage occurs during a wr
7070

7171
## Session consistency guarantees
7272

73-
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 has not 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 hub region to ensure session consistency.
73+
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 has not 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.
7474

7575
## Transient connectivity issues on TCP protocol
7676

0 commit comments

Comments
 (0)