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 is not working post Pega 7.1.7 upgrade

SA-9435

Summary



User is upgrading to Elasticsearch in Pega7.1.7 and while re-indexing, user encounters Connection timed out error.

Error Messages



PegaRULES Request Status fail Connection timed out.

Caused by: com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: com.pega.apache.http.conn.HttpHostConnectException: Connection to https://hostname:443 refused
at com.pegarules.generated.activity.ra_action_invokehttpconnector_xxxxxxx.step3_circum0(ra_action_invokehttpconnector_xxxxx.java:1558)
at com.pegarules.generated.activity.ra_action_invokehttpconnector_xxxxxxxx.perform(ra_action_invokehttpconnector_xxxxxx.java:103)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
… 
Caused by: java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

Steps to Reproduce



Upgrade to Elasticsearch in Pega 7.1.7 version.

Root Cause



Reported error appears frequently since Elastic search is not applied and system is using Lucene. Using Http connection to connect to the indexed node and soap service calls. This error is resolved by temporarily whitelisting the node URL.

Resolution



Reported issue is resolved through the following Local-change:
1.Configure the primary indexed node.
2.Make sure that all the nodes are configured with correct and full directory path for indexing location.
3.Search for the Dynamic System Settings - DSS ‘indexing/distribution/search_enabled’ and set it to true for all nodes.
4.Search for the Dynamic System Settings - DSS ‘indexing/distribution/index_enabled’ and set it to 'true' only for primary/indexed node and for rest of the nodes set it to 'false'.

 
DSS once set on a node is applied for all the nodes, the last step is to make sure that there is one node specific as our primary node.
Once index_enabled is enabled on primary node, add it on search setting landing page, perform re-indexing for the primary node.
When you add the remaining nodes, it replicates the DSS and indexing files from the primary node.

As index_enabled DSS is set to true for rest of the nodes once you add them after adding primary node.

 

Published June 18, 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