Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Search infrastructure takes longer to start after upgrade



After upgrading to Pega 7.1.8, the Search infrastructure which is a part of the startup sequence takes longer in a multinode environment than it did in Pega 7.1.7.

This can be seen by comparing the time in the logfiles between the line stating, "Starts Initializing Search Infrastructure" and the line stating, "Ends Initializing Search Infrastructure" as shown below:

08 May 2015 23:30:42,281 [ servername] ( internal.mgmt.PRNodeImpl) INFO - Starts Initializing Search Infrastructure
08 May 2015 23:37:18,667 [ servername] (.internal.PRSearchProviderImpl) INFO - Initialized full text search functionality for this node.
08 May 2015 23:37:18,667 [ servername] ( internal.mgmt.PRNodeImpl) INFO - Ends Initializing Search Infrastructure

Error Messages

Not Applicable

Steps to Reproduce

Restart all the nodes in a multinode system to observe this issue.

Root Cause

The root cause of this problem is a misconfiguration in the operating environment. 


Performing restarts with the Primary Search Node(s) starting up first (one followed by another, after the first is initialized) appears to help with system startup for the other nodes.

The explanation for this behavior is as follows:

When you have a multi-node environment and one or more indexing nodes, the primary search node (the one defined first when setting up the ElasticSearch process) must be started first. You must wait until the Search Initialization Infrastructure has started up before starting the next indexing node and repeat until all indexing nodes are started. All remaining non-indexing nodes can then be started up in parallel or sequentially. 

When the indexing nodes start, review the logfiles for content indicated that the Search Initialization Infrastructure has started.

If this process is not followed, elongated startup times are observed as the engine code looks for the primary search indexing nodes and waits and checks in 30 seconds interval until it finds the node(s).

If you need to stop a primary indexing node and restart it for any reason, shut down all the other nodes first and then restart the nodes in the order referenced above.

Published July 3, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

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