Skip to main content

Increase search indexing performance using a queue processor (8.2)

Suggest edit Updated on May 3, 2021

Search indexing now uses a queue processor, resulting in a significant performance improvement. In addition, indexing is restartable. For example, if the database goes down during indexing, indexing automatically restarts when the database becomes available, saving time because you do not have to manually start reindexing from scratch.

Note: Search processing in multitentant systems has not been updated to use the queue processor.

As a result of using the queue processor for indexing, the following changes have been made to the Search landing page:

  • You cannot cancel indexing from the Search landing page. Cancel indexing by stopping the queue processor from the Data flow landing page.
  • The progress message is not shown. View progress on the Queue Processor landing page.
  • Queue processor information has been added.
Thumbnail

Search landing page

For more information, see Stopping or pausing search reindexing.

  • Previous topic Improve editable data page performance using high-throughput mode (8.2)
  • Next topic Enhance report performance with new Elasticsearch features (8.2)
Did you find this content helpful? YesNo

33% found this useful

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us