Question
Transport for NSW
AU
Last activity: 19 Feb 2020 11:36 EST
Search has problems after upgrading to Pega 8.3
We've upgraded our pega from 722 to 8.3 and found that after upgrade the search indexing is not working properly - Though it looks like the indexing has started it seems that it has problems and never finishes.
All the pre-requisites that are required for search to work are there - like adding search node with directory and stream nodes status is normal. Even the JVM startup log shows that 'Finished configuration of node for full-text search, with no errors'.
Steps
- Upgraded from 722 to 83
- Started JVM
- In the search landing page added a node and file directory and status shows online
- Stream tab under 'Decisioning: Services' landing page shows a node with normal status
- Under Data flow tab, when Search service is selected, it shows the Data flow status as normal.
- pyFTSIncrementalIndexer queue process is also running
We've upgraded our pega from 722 to 8.3 and found that after upgrade the search indexing is not working properly - Though it looks like the indexing has started it seems that it has problems and never finishes.
All the pre-requisites that are required for search to work are there - like adding search node with directory and stream nodes status is normal. Even the JVM startup log shows that 'Finished configuration of node for full-text search, with no errors'.
Steps
- Upgraded from 722 to 83
- Started JVM
- In the search landing page added a node and file directory and status shows online
- Stream tab under 'Decisioning: Services' landing page shows a node with normal status
- Under Data flow tab, when Search service is selected, it shows the Data flow status as normal.
- pyFTSIncrementalIndexer queue process is also running
Please see the attached doc with screenshots.
Though things seem to be configured correctly the indexing seems to have a problem though it has been more than 2 days since it is up, we don't find indexing completed.
Are we missing anything.
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
***Edited by Moderator Marissa to update Product/Version; change from General to Product type***
Pegasystems Inc.
IN
pyBatchIndexprocessor queue size is around 4k and the processed items are zero. The processor might not be processing the queue items. Click on ViewDataFlow and see if the status is In Progress
Capgemini Engineering
BE
I think you first need to have the indexing done for Rules & Data (work leads to huge space used)
I would suggest to put /pegatmp/PegaSearchIndex for the file directory
If you've got one, you could stop all nodes, clear it this search, restart your search node and start re-indexing.
When indexing will be complete incremental indexer should then be working.
Regards
Anthony