Skip to content

Commit 65d1ead

Browse files
committed
Updates
1 parent fdaede1 commit 65d1ead

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/reliability/reliability-cosmos-db-nosql.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,11 +37,11 @@ You can enable zone redundancy in Azure regions that supports availability zones
3737

3838
The impact of zone redundancy on the high availability of your Cosmos DB for NoSQL database depends on the consistency level of the account and which regions have zone redundancy enabled. Consult the table below to estimate the impact of using availability zones in your account configuration:
3939

40-
| Account consistency level | Regions with availability zones enabled| Impact of using availability zones|
40+
| Regions with availability zones enabled | Account consistency level | Impact of using availability zones|
4141
|----|---|---|
4242
| Single region | All | **High benefit to zone redundancy.** Single region cannot benefit from multi-region failover capability. Enabling zone reudndancy guards against total availability loss due to the failure of an availability zone.|
4343
| Write regions and any number of secondary regions | All | **High benefit of zone redundancy.** Ensures greater availability for write operations for availability zone failures. |
44-
| One secondary read region | Synchronous (Strong) | **High benefit of zone redundancy.** Provides greater value because the loss of a read region in this scenario can impact write availability.|
44+
| One secondary read region | [Synchronous (Strong)](/azure/cosmos-db/consistency-levels#strong-consistency) | **High benefit of zone redundancy.** Provides greater value because the loss of a read region in this scenario can impact write availability.|
4545
| Two or more secondary read regions | [Synchronous (Strong)](/azure/cosmos-db/consistency-levels#strong-consistency) | **Less value of zone redundancy.** Provides marginal value because the system can leverage dynamic quorum should a read region lose availability which allows for writes to continue.|
4646
| One or more secondary read regions | [Asynchronous (Bounded Staleness or weaker)](/azure/cosmos-db/consistency-levels#bounded-staleness-consistency) | **Less value of zone redundancy.** Provides minimal value because the SDK already provides seamless redirects for reads when a read region fails.|
4747

@@ -91,6 +91,8 @@ To enable availability zone support you can use:
9191

9292
* [Azure Resource Manager templates](/azure/cosmos-db/manage-with-templates)
9393

94+
<a name="migrate-to-availability-zone-support">
95+
9496
#### Enable availability zone support
9597

9698
To learn how to enable zone redundancy on your Azure Cosmos DB account, see [Migrate Azure Cosmos DB for NoSQL to availability zone support](./migrate-cosmos-nosql.md)).

0 commit comments

Comments
 (0)