Skip to content

Commit 820e8da

Browse files
authored
Update search-indexer-troubleshooting.md
Updating with expectations about parallel indexing with built-in indexers.
1 parent 277dae1 commit 820e8da

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/search/search-indexer-troubleshooting.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: cognitive-search
99
ms.custom:
1010
- ignite-2023
1111
ms.topic: conceptual
12-
ms.date: 01/11/2024
12+
ms.date: 06/17/2024
1313
---
1414

1515
# Indexer troubleshooting guidance for Azure AI Search
@@ -266,6 +266,11 @@ Conditions under which a document is processed twice is explained in the followi
266266

267267
In practice, this scenario only happens when on-demand indexers are manually invoked within minutes of each other, for certain data sources. It can result in mismatched numbers (like the indexer processed 345 documents total according to the indexer execution stats, but there are 340 documents in the data source and index) or potentially increased billing if you're running the same skills for the same document multiple times. Running an indexer using a schedule is the preferred recommendation.
268268

269+
## Parallel indexing
270+
271+
When multiple indexers are operating simultaneously, it's typical for some to enter a queue, waiting for available resources to begin execution. The number of indexers that can run concurrently depends on several factors. If the indexers are not linked with [skillsets](cognitive-search-working-with-skillsets.md), the capacity to run in parallel relies on the number of [replicas and partitions](search-capacity-planning.md#concepts-search-units-replicas-partitions) set up in the AI Search service.
272+
273+
On the other hand, if an indexer is associated with a skillset, it operates within the AI Search's internal clusters. The ability to run concurrently in this case is determined by the complexity of the skillset and whether other skillsets are running simultaneously. Built-in indexers are designed to reliably extract data from the source, so no data is missed if running on a schedule. However, it is expected that the indexer processes of parallelization and scaling out may require some time.
269274

270275
## Indexing documents with sensitivity labels
271276

0 commit comments

Comments
 (0)