Agile Studio queue processor pyFTSIncrementalIndexer is not processing scheduled processes going back to 5/24/2023

General
, , , ,
1

There are 884 scheduled processes just sitting there for pyFTSIncrementalIndexer. Also, there are scheduled processes for pzStandardProcessor and pyProcessNotification and broken processes for pyBatchIndexProcessor (as see in attachment).

Don’t know if these are causing an issue with pyFTSIncrementalIndexer or visa versa.

All queue processors are “running”, so why aren’t they processing these scheduled processes?

PegaASQueueProcessorsScheduledProcesses_06052023.jpg
PegaASQueueProcessorsScheduledProcesses_06052023.jpg1581×214 60.4 KB

2

@SonyaS12 did you go through the logs?

Please could you go through the following support document?

pyFTSIncrementalIndexer not running or turning off automatically

The main documentation can be found here:

Managing queue processors

From the FAQ:

Why is my new queue processor not working?

If your queue processor does not work, consider the following:

  • Queue processor rules rely on the DSM service. In Pega Cloud services and client-managed cloud environments, a stream node is automatically configured and ready to use. For on-premises environments, ensure that you define at least one node in a cluster to be a Stream node using the setting: -DNodeType=Stream. For more information, see Stream node configurations for a queue processor rule.
  • One problem may be that Pega Platform is not be able to properly resolve your queue processor rule. For more information on how queue processor rules work, see System Runtime Context and General system settings.
  • If further troubleshooting is necessary, see Troubleshooting background processing.

There is also a good Pega Academy course: Background process management

3

@MarijeSchillern The issue is that we have recently done an upgrade and there is quite a bit of bumpiness. First, the Stream Service keeps going down (still happening pretty much every day), so we re-start it. Second, the Search settings keep having to be re-entered for the Host Node ID and File Directory. Once those 2 things are done, it seems to work correctly.