Question
Centene
US
Last activity: 11 Mar 2021 4:30 EST
Error: Stream service is not running in the cluster.
In our cloud development environment, we notice the error "Error: Stream service is not running in the cluster. in Admin Studio under "System & Nodes".
What wrong configuration is causing this error?
Accepted Solution
Pegasystems Inc.
US
What version?
For the Queue Processor to work in the cluster, it requires 3 node types (BackgroundProcessing, Search, and Stream), you do not have that here.
Maybe you should try Universal instead (-DNodeType=Universal) ? This specifies that the node is assigned all node types. Or else add more nodes until you meet the 3 required types
Pegasystems Inc.
US
Is this pegacloud or your own on-prem cloud? In any case, you need to start a stream node (-DNodeType=Stream), which is required for pega 8.x.
Louis Dreyfus Company
FR
Hello,
Hello,
1. It is not recommended to disable Stream nodes.
Disabling of Stream nodes can be done by selecting a different node type but it will break existing queue processors (It mean losing the ability to use FTS etc.)
the links below should give You further details to understand the topic:
https://community.pega.com/sites/default/files/help_v81/procomhelpmain.htm#rule-/rule-async-/rule-async-queueprocessor/main.htm
https://community.pega.com/knowledgebase/queue-processor-faq
https://community.pega.com/knowledgebase/articles/kafka-streaming-service
https://community.pega.com/knowledgebase/articles/stream-service-overview
https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#dsm/tasks/dsm-node-configuring-stream-service-tsk.htm
https://community.pega.com/sites/default/files/help_v74/procomhelpmain.htm#dsm/references/dsm-stream-service-node-overview-ref.htm
2. Stream node is required to run queue processor (QP) since Pega 8.
OOTB we ship 3 QPR (pyProcessNotification, pzStandardProcessor and pyFTSIncrementalIndexer).
These are fundamental for Platform's correct functioning. without a stream node, they can't be executed
So, in single-node environment, You can omit the nodetype (or run with universal nodeType). In a multi node, You need at least one Stream node.
You can verify if it's working properly by going to Configure ==> Decisioning ==> Infrastructure
Then click on stream and be sure one node is active there.
Once it's ok, go to Data Flow ( still under infrastructure ) and verify that you have one node for BackgroundProcessing and Search
After that it should be good.
Loïc
Accepted Solution
Pegasystems Inc.
US
What version?
For the Queue Processor to work in the cluster, it requires 3 node types (BackgroundProcessing, Search, and Stream), you do not have that here.
Maybe you should try Universal instead (-DNodeType=Universal) ? This specifies that the node is assigned all node types. Or else add more nodes until you meet the 3 required types
Louis Dreyfus Company
FR
Energy Safe Australia
AU
We are also facing the same issue, we got one node set as Stream,BackgroundProcessing,WebUser,Search and another as just WebUser. The nodes are running NORMAL (Stream,Search,BackgroundProcessing) initially and after few hours only WebUser is working and we are getting thread dumps and on restart below errors
0-05-10 13:49:32,134 [1,10,19,2,3,4,7,8,9]] [ STANDARD] [ ] [ ] (w.listener.RetryLoggerListener) ERROR - [pyFTSIncrementalIndexer] Preparing retry 1. Next attempt in 1s on data flow [pyFTSIncrementalIndexer] on stage [InputStage] with affected partitions: [0, 1, 10, 19, 2, 3, 4, 7, 8, 9] java.util.concurrent.CompletionException: com.pega.fnx.stream.spi.StreamServiceException: Stream SPI error at java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source) ~[?:1.8.0_201] at java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source) ~[?:1.8.0_201] at java.util.concurrent.CompletableFuture$AsyncSupply.run(Unknown Source) ~[?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_201] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_201] at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]
Bien Etre assistance
FR
Hi @DharanitharanR5430, I have the same issue, have you solved it?