Skip to main content

 locked
Azure Search - Concurrent requests to run indexer failing RRS feed

  • Question

  • 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.


    Thursday, May 23, 2019 11:41 PM

All replies

  • 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

    Saturday, May 25, 2019 9:45 AM
    Moderator