Skip to content

Commit 91a0d60

Browse files
committed
Updates
1 parent 8a5c2f7 commit 91a0d60

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/reliability/reliability-ai-search.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ The addition of multiple replicas allows AI Search to:
4141

4242
You can also configure the number of *partitions*, which represent the storage used by the search indexes.
4343

44-
For more information about replicas and partitions, see [Estimate and manage capacity of a search service](/azure/search/search-capacity-planning#add-or-remove-partitions-and-replicas).
44+
It's important to understand the impact of adding replicas and partitions, because they each affect read and write performance in different ways. For more information about replicas and partitions, see [Estimate and manage capacity of a search service](/azure/search/search-capacity-planning).
4545

4646
## Transient faults
4747

@@ -51,7 +51,7 @@ Azure AI Search indexers have built-in transient fault handling. If a data sourc
5151

5252
Search services might experience transient faults during standard, unscheduled maintenance operations. Azure AI Search doesn't provide advance notification or allow scheduling of maintenance at specific times. Although every effort is made to minimize downtime, even for single-replica services, brief interruptions can still occur. To improve resiliency against these transient faults, we recommend that you use two or more replicas.
5353

54-
Any applications you build that interact with Azure AI Search should handle transient faults for both read and write operations.
54+
Any applications you build that interact with Azure AI Search should handle transient faults. Use a retry strategy, with exponential backoffs, for both read and write operations.
5555

5656
## Availability zone support
5757

0 commit comments

Comments
 (0)