Skip to content

Commit 0bcaaab

Browse files
Acro fixes
1 parent af75dc3 commit 0bcaaab

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
@@ -85,7 +85,7 @@ Zone redundancy is automatically enabled when your search service meets all of t
8585

8686
Azure AI Search attempts to place replicas across different availability zones. However, there are occasionally situations where all of the replicas of a search service might be placed into the same availability zone. This situation can happen when replicas are removed from your service, such as when you *scale in* by configuring your service to use fewer replicas. The reason is that replica removal currently doesn't cause the remaining replicas to be rebalanced across the availability zones.
8787

88-
To reduce the likelihood of all of your replicas being placed into a single availabilty zone, you can manually trigger a scale-out operation immediately after a scale-in operation. For example, suppose your search service has ten replicas and you want to scale in to seven replicas. Instead of performing a single scale operation, you can temporarily scale to six instances, then immediately scale to seven instances, to trigger zone rebalancing.
88+
To reduce the likelihood of all of your replicas being placed into a single availability zone, you can manually trigger a scale-out operation immediately after a scale-in operation. For example, suppose your search service has ten replicas and you want to scale in to seven replicas. Instead of performing a single scale operation, you can temporarily scale to six instances, then immediately scale to seven instances, to trigger zone rebalancing.
8989

9090
### Cost
9191

@@ -97,7 +97,7 @@ If your search service meets the [requirements for zone redundancy](#requirement
9797

9898
### Capacity planning and management
9999

100-
To prepare for availability zone failure, consider *over-provisioning* the number of replicas. Over-provisioning allows the your search service to tolerate some degree of capacity loss and continue to function without degraded performance. Adding replicas during an outage is challenging, so over-provisioning helps ensure that your search service can handle normal request volumes, even with reduced capacity. For more information, see [Manage capacity with over-provisioning](/azure/reliability/concept-redundancy-replication-backup#manage-capacity-with-over-provisioning).
100+
To prepare for availability zone failure, consider *over-provisioning* the number of replicas. Over-provisioning allows the search service to tolerate some degree of capacity loss and continue to function without degraded performance. Adding replicas during an outage is challenging, so over-provisioning helps ensure that your search service can handle normal request volumes, even with reduced capacity. For more information, see [Manage capacity with over-provisioning](/azure/reliability/concept-redundancy-replication-backup#manage-capacity-with-over-provisioning).
101101

102102
### Normal operations
103103

0 commit comments

Comments
 (0)