ERROR - Cannot start service [StreamServer.Default]. Will retry in 180 seconds. Remaining attempts: 2 com.pega.dsm.dnode.api.StreamServiceException: Unable to start Kafka broker. Last state was: NotConnected [2024-07-19 19:11:38,908] ERROR Fatal error d

Hi Everyone,

Just want to share the latest learnings during Pega upgrade from Pega 7.1.9 to Pega 8.8.3.

Post upgrading DB using in place upagrade method, when we tried to get the environment up by deploying prweb, we have got below exception. Up on investigation found that issue is happening due to the issue with pyprnodeID length.

Issue Description:

ERROR - Cannot start service [StreamServer.Default]. Will retry in 180 seconds. Remaining attempts: 2
com.pega.dsm.dnode.api.StreamServiceException: Unable to start Kafka broker. Last state was: NotConnected
[2024-07-19 19:11:38,908] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)kafka.zookeeper.ZooKeeperClientTimeoutException: Timed out waiting for connection

Root cause:

-Didentification.nodeid=XXXXX

54 chars too big to fit in the table for the stream sessions “PYPRNODEID” VARCHAR2(50 CHAR)

CREATE TABLE “XXXX”.“PR_DATA_STREAM_SESSIONS”
( “PYUUID” VARCHAR2(36 CHAR) NOT NULL ENABLE,
“PYID” NUMBER(19,0),
“PYTIMEOUT” NUMBER(19,0),
“PYSTARTTIME” NUMBER(19,0),
“PYLASTSEENDATETIME” NUMBER(19,0),
“PYPRNODEID” VARCHAR2(50 CHAR),
CONSTRAINT “PR_DATA_STREAM_SESSIONS_PK” PRIMARY KEY (“PYUUID”)

Solution: Increase/Decrease the size of the PYPRNODEID column to fit the nodeid

@Eswar KK please log a support ticket via the MSP and provide the INC id here so we can help track it.