Skip to main content
LinkedIn
Copied!

Table of Contents

Configuring index host nodes

Version:

Only available versions of this content are shown in the dropdown

In a multi-node clustered system, the index files required for search can be hosted on one or more nodes. To ensure high reliability and minimize search query downtime, configure at least two, and preferably three nodes as search host nodes.

For a new installation, allocate at least 1 GB of free space for the search index files. For an upgrade, allocate three times the amount of space previously configured on the Search landing page for index files. This extra space is recommended to optimize performance.

If you add a host node, wait until the new node is displayed with Node Status equal to online before configuring additional nodes. Click Refresh to refresh the display.

You can add and delete index host nodes interactively. You can delete index nodes by using a script that uses a direct connection to the database.

For more information on configuring index host nodes interactively, see Configuring index host nodes from the user interface.

For more information on removing index host nodes by using a direct connection to the database, see Removing index host nodes by using a direct connection to the database.

  • Viewing index host node status

    You can see whether your index host nodes are offline or online by viewing the index host node status on the Search landing page.

  • Enabling and disabling encryption for communication among search nodes

    For on-premises deployments, enable encryption for communication among search nodes to prevent unauthorized access to the data that is transported across search nodes. By default, search is encrypted for cloud services and applications.

  • Viewing search agent information

    You can view the status of Pega-RULES agents that incrementally update the search index files as changes are made to Rules-, Data-, and/or Work- instances. This information is useful for troubleshooting. You can view the agent name, number of entries currently in the queue, and the age of the oldest entry in the queue for each agent.

  • Configuring automated search notifications

    You can periodically check the status of search agents and index files, and report on any events and issues that arise. The system sends out notifications when reindexing is complete or fails, when a period spot check fails, or when a full diagnostic check is complete or fails.

  • Configuring index host nodes from the user interface

    In a multinode cluster system, the index files required for search can be hosted on one or more nodes. To add or remove an index host node interactively, complete the following steps.

  • Removing index host nodes by using a direct connection to the database

    In a multinode cluster system, the index files required for search can be hosted on one or more nodes. To remove an index host node by using a direct connection to the database, complete the following steps.

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