Azure Cognitive Search indexer

Question

At random times, the indexer will continue running its current execution for much longer than normal. Usually it takes a few milliseconds to complete. However, sometimes it is saying that it is running for an hour or more, and at that point I need to reset the indexer and run it again manually.

The thing is, its not giving out any error when it does this.

Had anyone had similar case? Or input how can I produce logs other than the execution history.

Cheers,

Answer 1

@Eric ,

Just to clarify, do you receive any error message/warning in execution history? I understand that you have mentioned, the issue occurs randomly, are you facing this issue since the time of provisioning or only after any recent changes?

To begin with, on the Search Service, In the left navigation, click on Diagnose and solve problems – Checkout the tile highlighted files/troubleshooter recommendations (if you haven't done this already).

I’m not sure on what SKU (pricing tier) you’re using, you may see this doc ‘Estimate and manage capacity of an Azure Cognitive Search service’ – and based on your requirement, scale-up the tier. If a tier's capacity turns out to be too low, you'll need to provision a new service at a higher tier and then reload your indexes.

Answer 2

@Eric , Adding more info:

You may use Debug sessions (preview), it is a visual editor that works with an existing skillset in the Azure portal. Within a debug session you can identify and resolve errors, validate changes, and commit changes to a production skillset in the AI enrichment pipeline.

Tutorial: Debug a skillset using Debug Sessions

Note-A debug session only works with a single document. Since it is in preview, it’s not recommended for prod workloads.

Try increasing index throughput -For parallel indexing, place your data into multiple containers or multiple virtual folders inside the same container. Then create multiple data source and indexer pairs. All indexers can use the same skillset and write into the same target search index, so your search app doesn’t need to be aware of this partitioning.