Question
Proximus
BE
Last activity: 17 May 2021 6:21 EDT
PEGA 8.5.2 - Node Classification & Invalid configuration. Undefined stream provider end point
Hello,
On a full fresh environment upgrade from 8.2.x to 8.5.2 without any processing, I've set up a node as Search,WebUser,BackgroundProcessing.
It's a fresh install with all stream tables are empty.
The node mentioned above (Search,WebUser,BackgroundProcessing) is complaining with lots of : StreamServiceException: Invalid configuration. Undefined stream provider end point
for: [2/10/21 14:32:30:877 CET] 0000009b SystemOut O 2021-02-10 14:32:30,848 [,19,2,3,4,5,6,7,8,9]] [ STANDARD] [ ] [] (w.listener.RetryLoggerListener) ERROR - [pyProcessCaseEvents] Preparing retry 8. Next attempt in 2m on data flow [pyProcessCaseEvents] on stage [InputStage] with affected partitions: [0, 1, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 2, 3, 4, 5, 6, 7, 8, 9] [2/10/21 14:32:31:865 CET] 0000009b SystemOut O 2021-02-10 14:32:31,844 [,19,2,3,4,5,6,7,8,9]] [ STANDARD] [ ] [ ] (w.listener.RetryLoggerListener) ERROR - [pyBIBatchIndexClassesProcessor] Preparing retry 8. Next attempt in 2m on data flow [pyBIBatchIndexClassesProcessor] on stage [InputStage] with affected partitions: [0, 1, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 2, 3, 4, 5, 6, 7, 8, 9] and lots of others
Question: on any case with Pega8 we need to have one stream node up & running?
Thank you
Regards
Anthony
Hello,
On a full fresh environment upgrade from 8.2.x to 8.5.2 without any processing, I've set up a node as Search,WebUser,BackgroundProcessing.
It's a fresh install with all stream tables are empty.
The node mentioned above (Search,WebUser,BackgroundProcessing) is complaining with lots of : StreamServiceException: Invalid configuration. Undefined stream provider end point
for: [2/10/21 14:32:30:877 CET] 0000009b SystemOut O 2021-02-10 14:32:30,848 [,19,2,3,4,5,6,7,8,9]] [ STANDARD] [ ] [] (w.listener.RetryLoggerListener) ERROR - [pyProcessCaseEvents] Preparing retry 8. Next attempt in 2m on data flow [pyProcessCaseEvents] on stage [InputStage] with affected partitions: [0, 1, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 2, 3, 4, 5, 6, 7, 8, 9] [2/10/21 14:32:31:865 CET] 0000009b SystemOut O 2021-02-10 14:32:31,844 [,19,2,3,4,5,6,7,8,9]] [ STANDARD] [ ] [ ] (w.listener.RetryLoggerListener) ERROR - [pyBIBatchIndexClassesProcessor] Preparing retry 8. Next attempt in 2m on data flow [pyBIBatchIndexClassesProcessor] on stage [InputStage] with affected partitions: [0, 1, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 2, 3, 4, 5, 6, 7, 8, 9] and lots of others
Question: on any case with Pega8 we need to have one stream node up & running?
Thank you
Regards
Anthony
Wagner Development Solutions
HU
@Anthony_GourtayI have the same issue. I found that default replication factor is set to 2 and when you click on the settings icon on the streaming node, it complains about it (since we have only one node).
I thought setting the replication factor to 1 would solve the issue but it didn't. The system works for some time (usually for about 1 week) then the streaming node crashes.
Did you find any solution for this issue?
Thanks a lot!
Proximus
BE
Hello,
For my issue, I found that a stream node is mandatory so in any case, you'll need at least one node with nodeType "Stream" (on top of other roles)
If you've got several applications on same server running with PEGA8.5, then you'll also need to tune ports for each application, or stream setup/start will fail
Default ports <env name="dsm/services/stream/pyBrokerPort" value="9092" /> <env name="dsm/services/stream/pyKeeperPort" value="2181" /> <env name="dsm/services/stream/pyJmxPort" value="9999" /> <env name="dsm/services/stream/pyPort" value="7003" />
For another app on same server, I've just put -1 for all above values
I also cleared some stream log failures by clearing pegatemp dir.. When node name changes, then it keeps some ref of previous nodes and clearing pegatemp clears errors..
Hope this helps
Regards
Anthony