You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-howto-run-reset-indexers.md
+35-4Lines changed: 35 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ manager: nitinme
7
7
ms.author: heidist
8
8
ms.service: azure-ai-search
9
9
ms.topic: how-to
10
-
ms.date: 08/27/2025
10
+
ms.date: 09/01/2025
11
11
ms.update-cycle: 180-days
12
12
ms.custom:
13
13
- ignite-2023
@@ -26,7 +26,7 @@ This article explains how to run indexers on demand, with and without a reset. I
26
26
27
27
## How indexers connect to Azure resources
28
28
29
-
Indexers are one of the few subsystems that make overt outbound calls to other Azure resources. You can use keys or roles to authenticate the connection.
29
+
Indexers are one of the few subsystems that make overt outbound calls to other Azure resources. Depending on the external data source, you can use keys or roles to authenticate the connection.
30
30
31
31
In terms of Azure roles, indexers don't have separate identities: a connection from the search engine to another Azure resource is made using the [system or user-assigned managed identity](search-how-to-managed-identities.md) of a search service, plus a role assignment on the target Azure resource. If the indexer connects to an Azure resource on a virtual network, you should create a [shared private link](search-indexer-howto-access-private.md) for that connection.
32
32
@@ -272,7 +272,6 @@ While using either "reset" or "reset docs" can address this issue, "reset" can b
272
272
273
273
Resync Indexers offers an efficient and convenient alternative. Users simply place the indexer in resync mode and specify the content to resynchronize by calling the resync indexers API. In the next run, the indexer will inspect only relevant portion of data in the source and avoid any unnecessary processing that is unrelated to the specified data. It will also query the existing documents in the target index and only update the documents that show discrepancies between the data source and the target index. After the resync run, the indexer will be synchronized and revert to regular indexer run mode for subsequent runs.
274
274
275
-
276
275
### How to resync and run indexers
277
276
278
277
1. Call [Indexers - Resync](/rest/api/searchservice/indexers/resync?view=rest-searchservice-2025-08-01-preview&preserve-view=true) with a preview API version to specify what content to re-synchronize.
@@ -295,7 +294,7 @@ Resync Indexers offers an efficient and convenient alternative. Users simply pla
295
294
296
295
To check reset status and to see which document keys are queued up for processing, following these steps.
297
296
298
-
1. Call [Get Indexer Status](/rest/api/searchservice/indexers/get-status?view=rest-searchservice-2024-05-01-preview&preserve-view=true) with a preview API.
297
+
1. Call [Get Indexer Status](/rest/api/searchservice/indexers/get-status?view=rest-searchservice-2025-08-01-preview&preserve-view=true) with a preview API.
299
298
300
299
The preview API will return the **`currentState`** section, found at the end of the response.
301
300
@@ -325,6 +324,38 @@ To check reset status and to see which document keys are queued up for processin
325
324
326
325
1. After the documents are reprocessed, run Get Indexer Status again. The indexer returns to the **`indexingAllDocs`** mode and will process any new or updated documents on the next run.
327
326
327
+
## Check indexer runtime quota for S3 HD search services
328
+
329
+
Applies to search services at the Standard 3 High Density (S3 HD) pricing tier.
330
+
331
+
To help you monitor indexer running times relative to the 24-hour window, [Get Service Statistics](/rest/api/searchservice/get-service-statistics/get-service-statistics#servicestatistics?view=rest-searchservice-2025-08-01-preview&preserve-view=true) and [Get Indexer Status](/rest/api/searchservice/indexers/get-status?view=rest-searchservice-2025-08-01-preview&preserve-view=true) now return more information in the response.
332
+
333
+
### Track cumulative runtime quota
334
+
335
+
Track a search service's cumulative indexer runtime usage and determine how much runtime quota is left within the current 24-hour window period.
336
+
337
+
Send a GET request to the search service resource provider. For help with setting up a REST client and getting an access token, see [Connect to a search service](/azure/search/search-get-started-rbac?pivots=rest).
338
+
339
+
```http
340
+
GET {{search-endpoint}}/servicestats?api-version=2025-08-01-preview
341
+
Content-Type: application/json
342
+
Authorization: Bearer {{accessToken}}
343
+
```
344
+
345
+
Responses include `indexersRuntime` properties, showing start and end times, seconds used, seconds remaining, and cumulative runtime within the last 24 hours.
346
+
347
+
### Track indexer runtime quota
348
+
349
+
Return the same information for a single indexer.
350
+
351
+
```http
352
+
GET {{search-endpoint}}/indexers/hotels-sample-indexer/search.status?api-version=2025-08-01-preview
353
+
Content-Type: application/json
354
+
Authorization: Bearer {{accessToken}}
355
+
```
356
+
357
+
Responses include a `runtime` properties, showing start and end times, seconds used, and seconds remaining.
358
+
328
359
## Next steps
329
360
330
361
Reset APIs are used to inform the scope of the next indexer run. For actual processing, you'll need to invoke an on-demand indexer run or allow a scheduled job to complete the work. After the run is finished, the indexer returns to normal processing, whether that is on a schedule or on-demand processing.
Copy file name to clipboardExpand all lines: articles/search/whats-new.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ Learn about the latest updates to Azure AI Search functionality, docs, and sampl
30
30
|[Answer synthesis (preview)](search-agentic-retrieval-how-to-synthesize.md)| Agentic search | New `answerSynthesis` modality for knowledge agents. When specified, an LLM generates a natural-language answer as an embedded step in the retrieval pipeline. This differs from the default `extractiveData` modality, which returns raw search results for downstream processing. |
31
31
|["Fast path" for knowledge agents (preview)](search-knowledge-source-overview.md#attempt-fast-path-processing)| Agentic search | New `attemptFastPath` boolean for knowledge agents. Enables a shorter processing time if queries are concise and the initial response is sufficiently relevant. |
32
32
|[Retrieval instructions (preview)](search-agentic-retrieval-how-to-create.md)| Agentic search | New `retrievalInstructions` property for knowledge agents guides query planning in an agentic retrieval workflow. For example, you can specify criteria for including or excluding specific knowledge sources. |
33
-
|[Improved indexer runtime tracking information (preview)](search-howto-run-reset-indexers.md)| Indexers |[Get Service Statistics](/rest/api/searchservice/get-service-statistics/get-service-statistics?view=rest-searchservice-2025-08-01-preview&preserve-view=true) response now provides cumulative indexer processing information for the entire service. [Get Status - Indexers](/rest/api/searchservice/get-service-statistics/get-status?view=rest-searchservice-2025-08-01-preview&preserve-view=true) provides the same information, but for a specific indexer. |
33
+
|[Improved indexer runtime tracking information (preview)](search-howto-run-reset-indexers.md#check-indexer-runtime-quota-for-s3-hd-search-services)| Indexers | Applies to Standard 3 High Density (S3 HD) services only.[Get Service Statistics](/rest/api/searchservice/get-service-statistics/get-service-statistics?view=rest-searchservice-2025-08-01-preview&preserve-view=true) response now provides cumulative indexer processing information for the entire service. [Get Status - Indexers](/rest/api/searchservice/get-service-statistics/get-status?view=rest-searchservice-2025-08-01-preview&preserve-view=true) provides the same information, but for a specific indexer. |
34
34
|[Strict postfiltering for vector queries (preview)](vector-search-filters.md)| Vector search | New `strictPostFilter` mode for the `vectorFilterMode` parameter. When specified, filters are applied after the global top-`k` vector results are identified, ensuring that returned documents are a subset of the unfiltered results. |
35
35
|[Increased maximum dimensions for vector fields](search-limits-quotas-capacity.md#index-limits)| Vector search | The maximum dimensions per vector field are now `4096`. This update applies to all stable and preview REST API versions that support vectors and doesn't introduce breaking changes. |
0 commit comments