Support Article
pyFTSIncrementalIndexer exception
SA-102330
Summary
pyFTSIncrementalIndexer agent fails with an exception.
Error Messages
com.pega.pegarules.pub.context.QueueProcessorManagementOperationsException: Queue processor: pyFTSIncrementalIndexer cannot be started as it is in '-' state at com.pega.platform.executor.queueprocessor.internal.QueueProcessorManagementOperationsImpl.startQueueProcessor(QueueProcessorManagementOperationsImpl.java:682) at com.pega.pegarules.management.internal.system.operations.QueueProcessorManagementAPI.startQueueProcessor(QueueProcessorManagementAPI.java:73) at com.pega.platform.pegasearch.indexer.internal.DistributedIndexerAgent.manageIncrementalIndexer(DistributedIndexerAgent.java:168) at com.pega.pegarules.session.internal.mgmt.Executable.manageIncrementalIndexer(Executable.java:11531) at com.pegarules.generated.activity.ra_action_pzmanageincrementalindexer_d9e9e83456741456f82b053b64afce4f.step1_circum0(ra_action_pzmanageincrementalindexer_d9e9e83456741456f82b053b64afce4f.java:163) at com.pegarules.generated.activity.ra_action_pzmanageincrementalindexer_d9e9e83456741456f82b053b64afce4f.perform(ra_action_pzmanageincrementalindexer_d9e9e83456741456f82b053b64afce4f.java:72)
Steps to Reproduce
Unknown
Root Cause
The pyFTSIncrementalIndexer Queue Processor did not execute and '- -' displayed in the Queue Processor status. When the JVM was restarted, it attempted to verify the pyFTSIncrementalIndexer Queue Processor instance on the other Decision Strategy Manager (DSM) nodes. However, it was unable to find the instance. Therefore, the exception displayed.
Resolution
Perform the following local-change:
- Use the 'pxStartRunByID' (DDF) activity.
- Provide the 'pyFTSIncrementalIndexer' instance ID to run the activity. The 'pyFTSIncrementalIndexer' queue processor changes to the Running state.
Published March 5, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.