Question
HMSA
US
Last activity: 27 Jan 2017 1:40 EST
pr_sys_statusnodes pyIndexDirectory becomes NULL after upgrading from 717 to 722
After upgrading from 717 to 722 and restarting our application server we notice that the pyIndexDirectory has NULL in pr_sys_statusnodes table. Prior to restarting pyIndexDirectory was "X:\Program Files\Pega Systems\Index"
Upon restarting the server the value became: "X:\Program Files\Pega Systems\TempDir\PegaSearchIndex". On the Search landing page we see that Indexing has started. We cancel the index and changed the Search Index file directory back to original: "X:\Program Files\Pega Systems\Index". Doing Check of the rules, data, and work show indexes are good. The pr_sys_statusnodes pyIndexDirectory als has correct directory.
But every time the appliction server is restarted the pyIndexDirectory goes to NULL and the directory changes to the TempDir path.
Does anyone know why this is happening?
***Updated by moderator: Lochan to add SR details***
Accepted Solution
HMSA
US
What worked for us: Dynamic System Setting: indexing/distributed/automodecleanupandreindex = false
This stopped the Index Directory from being intialized to NULL on graceful shutdown of our application server and also stopped triggering automatic reindexing. Since the Index directory is not being intialized to NULL the currently set Index Directory is being preserved/retained.
Note: We could not get the -Dindex.directory=<path> to work but this is not needed in our case as the indexing/distributed/automodecleanupandreindex = false provides the desired behavior in our environment.
Pegasystems Inc.
IN
Hello ,
I am suspecting that there would be multiple entries in PR_SYS_STATUSNODES table for PYINDEXDIRECTORY .
check the below query and let us know the results
select * from PR_SYS_STATUSNODES where PYINDEXDIRECTORY is not null;
Thanks,
Arun
Pegasystems Inc.
IN
Hi Gerald,
Thank you for updating us with the SR number. I have updated your post above to reflect this information for effective tracking.
Regards,
Lochan | Community Moderator | Pegasystems Inc.
Pegasystems Inc.
IN
Posting the below snippet so it's usefule for other user's facing the issue.
This is an expected behavior for 7.2.2 release. This was done in-order to have the replica count appropriate so as to minimize the elasticsearch errors. https://pdn.pega.com/release-note/search-reindexing-automatically-triggered
It's advised that JVM argument -Dindex.directory=<path to index directory> be set to all nodes that are targetted to be index nodes to avoid re-configuring them as index nodes after every re-start
Accepted Solution
HMSA
US
What worked for us: Dynamic System Setting: indexing/distributed/automodecleanupandreindex = false
This stopped the Index Directory from being intialized to NULL on graceful shutdown of our application server and also stopped triggering automatic reindexing. Since the Index directory is not being intialized to NULL the currently set Index Directory is being preserved/retained.
Note: We could not get the -Dindex.directory=<path> to work but this is not needed in our case as the indexing/distributed/automodecleanupandreindex = false provides the desired behavior in our environment.