Question

2
Replies
39
Views
Close popover
Hari Radhakrishnan (HariR246)
ANZ

ANZ
AU
HariR246 Member since 2020 4 posts
ANZ
Posted: December 17, 2020
Last activity: December 18, 2020

Pega 8.5.1 upgrade - "StreamServiceException: Kafka data belongs to a node pega-stream-0 from the different cluster"

Hi,

1. Is the parameter, prconfig/cloud/isNodeAgnosticAdminStudio, only applicable to the web pods? Do you suggest that we use this parameter in our Openshift cluster running PEGA 8.5.1?

2. We faced issue with bring-up of stream pods after upgrade from 8.4.0 to 8.5.1 (on Openshift cluster). Do you have any suggestions on how to prevent the below exception from occurring during a production upgrade?

Workaround - After removing /opt/pega/kafkadata/prpc_node_id during stream pod startup, the pods are coming up. Would putting the 8.4 stream pods in Quiesce before scale-down, help to prevent this error from occurring after a in-place upgrade?

Cannot start service [StreamServer.Default]. Will retry in 180 seconds. Remaining attempts: 1][STACK][com.pega.dsm.dnode.api.StreamServiceException: Kafka data  belongs to a node pega-stream-0 from the different cluster 631a648e-9867-48bd-a00d-1c8ffd9d35d1
***Edited by Moderator Marissa to change type from Product to Upgrade; update Platform Capability tags***
***Edited by Moderator: Pooja Gadige to add platform capability tag***
Pega Platform 8.5.1 Decision Management System Administration Upgrades Data Integration Financial Services System Administrator Upgrade