Skip to content

Commit 29fc345

Browse files
committed
Adding link to failover and add/remove region info in throughput doc
1 parent f342fdb commit 29fc345

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/scaling-provisioned-throughput-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ When you send a request to increase the RU/s of your database or container, depe
3131
Each physical partition can support a maximum of 10,000 RU/s (applies to all APIs) of throughput and 50 GB of storage (applies to all APIs, except Cassandra, which has 30 GB of storage).
3232

3333
> [!NOTE]
34-
> If you perform a failover operation or add/remove a new region while an asynchronous scale-up operation is in progress, the throughput scale-up operation will be paused. It will resume automatically when the failover or add/remove region operation is complete.
34+
> If you perform a [manual region failover operation](how-to-manage-database-account.md#manual-failover) or [add/remove a new region](how-to-manage-database-account.md#addremove-regions-from-your-database-account) while an asynchronous scale-up operation is in progress, the throughput scale-up operation will be paused. It will resume automatically when the failover or add/remove region operation is complete.
3535
- **Instant scale-down**
3636
- For scale down operation Azure Cosmos DB doesn’t need to split or add new partitions.
3737
- As a result, the operation completes immediately and the RU/s are available for use,

0 commit comments

Comments
 (0)