Azure搜索 - 运行索引器失败的并发请求 [英] Azure Search - Concurrent requests to run indexer failing
问题描述
我有一个Azure搜索服务，在Blob存储上配置了一个索引和索引器，包含数千个文档（.txt，.pdf等）。每当我收到更新文档元数据的请求或将更多文档上传到blob
存储时，我必须按需运行索引器。但是，当多个人试图更新blob存储上的文档元数据时，我现在无法生成并发请求来运行索引器。当我这样做时，我得到以下异常：
另一个索引器调用正在进行中;不允许并发调用。
             相关异常：CloudException（0x80131500-另一个索引器调用当前正在进行中;不允许并发调用。）
我的情况是否有解决方案i。同时按需运行索引器。 。？
谢谢。
您是否可以跨多个索引器拆分内容？例如，如果您要存储专业体育联盟的文档，而不是将所有文档整合到整个联盟的单个索引器中，请将文档拆分，以便每个团队拥有自己的索引器
。这样，您可以降低运行相同索引器的风险。更多信息
Hi,
I have a Azure Search Service configured with one index and indexer on a Blob Storage with thousands of documents (.txt, .pdf etc). I have to run indexer on demand whenever I get a request to update the metadata of document or upload more documents to blob storage. But, right now I cannot make concurrent requests to run indexer when multiple people trying to update the metadata of documents on blob storage. When I do this I get following exception:
Another indexer invocation is currently in progress; concurrent invocations are not allowed.
Associated exception: CloudException (0x80131500- Another indexer invocation is currently in progress; concurrent invocations are not allowed.)
Is there a solution for my situation i.,e running indexer on demand concurrently.. ?
Thank you.
Would you be able to split your content out across multiple indexers? For example, if you are storing documents for a profession sports league, rather than lump all of the documents into a single indexer for the entire league, split the documents up so that each team has their own indexer. That way, you lower your risk of running the same indexer. More info here
You can speed up indexing by parallelizing it: split blobs in your container into several folders, and create several datasource / indexer pairs all writing into the same target search index. If your search service has N search units, N indexer can be running concurrently, resulting in a significant speed-up of indexing. Source
这篇关于Azure搜索 - 运行索引器失败的并发请求的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
