Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Reindexing a node in a cluster

Updated on July 8, 2022
Applicable to deployments with embedded Elasticsearch.

During reindexing, database performance might be affected and search results might be incomplete. This is due to the reindexing process.

When you reindex a node that belongs to a cluster, the system records each reindexing as an instance of the Log-Cluster-FTSIndex class, including the node ID and pyStatusWork, which is set to "Open-InProgress." After reindexing is complete, pyStatusWork is set to "Resolved-Completed" if there are no errors, or to "Resolved-Error" if there are errors.

To access the Search landing page, you must have the pxAccessSearchLP privilege, which is included in the PegaRULES:SysAdm4 role.

  • The pr_log_cluster table holds instances of the Log-Cluster-FTSIndex class derived from the Log-Cluster- class.
  • You cannot reindex from the command line utility if you have initiated reindexing in the same node or another node in the same cluster from the user interface, and reindexing is still in progress.
  • Previous topic Rebuilding search indexes by using a direct connection to the database
  • Next topic Integrating with Apache UIMA

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us