Skip to main content

Table of Contents

Reindexing a node in a cluster


Only available versions of this content are shown in the dropdown

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.
Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us