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

Re-indexing is not working after upgrade

SA-9687

Summary



Environment is upgraded from Pega 6.1 to Pega 7. While doing RULES Re-Index, Adminitrator observed following error in PegaRULES.log and indexing is not working

Pega has access to this location as the folder PegaRULESIndex & all the contents inside has been created by the server process itself.
[/%DiectoryLocation%/explicittempdir/PegaRULESIndex.
I have been informed that it is not a shared location either.

Already installed 
HFIX-21219 : System crashes due to native OOM on thread creation
and it’s dependent HFIX-20361 : Do not automatically build ES indices on upgrade

Administrator also observed that updating Search Index Host Node ID and Search Index File Directory is not possible from the Search landing Page.



Error Messages



2015-03-23 11:09:28,922 {ABSOLUTE} [ WebContainer : 4] [ PegaRULES:07.10] (.internal.PRSearchProviderImpl) ERROR XX.XX.XX.XXX|serverName
com.pega.pegarules.search.internal.es.FTSInitializationException: Failed to initialize full text search for this node.
Caused by:
com.pega.elasticsearch.ElasticsearchIllegalStateException: Failed to obtain node lock, is the following location writable?: [/%DiectoryLocation%r/PegaRULESIndex/f741deba299cacb26fc2eb2a4900b55c]



Steps to Reproduce



Try to Re-index rules - which isn't working.

Root Cause



It was observed that the Elastic Search is unable to get a lock on the node file. It tries about 50 times and this takes about 30 minutes before it moves on
Infrastructure team looked at the issue which looks to be a problem on file lock configuration in Linux for the NFS mounted drive where the index file is created. 
It works fine in another environment and there are some differences in the daemons that are running ("statd" daemon is running in the env that works, and is not in the env that doesn't).



Resolution



Infrastruture team started "statd" daemon process on this affected environment and now Rules Re-Index is working as expected.
Administrator is also able to update Search Landing Page details as required.

Published May 8, 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