I am not sure if this is a misconfiguration issue on our side.
We noticed in production the persistent queries that write in some streams had just disappeared for no particular reason.
When restarting ksqldb the streams were there, but the queries were missing and also their consumers. Also in the _command topic everything was there.
Please let me know what kind of information can i provide if it would be helpful.
To Reproduce
Steps to reproduce the behavior, include:
image: confluentinc/cp-ksqldb-server:6.2.0
we have 1 topic where we push incoming events (topic-1)
1 Pull stream using "topic-1" as its source (stream-1)
1 Push stream CSAS (stream-2) that reads and transforms from the pull stream "stream-1" and pushes to "stream-2" topic
We were working with this kind of setup for 1.5 years. The last migrations of the schemas was 1 month ago and yesterday, suddenly the persistent query writing to "stream-2" had zero consumers, even when restarting KSQL.
I am not sure if this is a misconfiguration issue on our side. We noticed in production the persistent queries that write in some streams had just disappeared for no particular reason. When restarting ksqldb the streams were there, but the queries were missing and also their consumers. Also in the _command topic everything was there. Please let me know what kind of information can i provide if it would be helpful.
To Reproduce Steps to reproduce the behavior, include:
image: confluentinc/cp-ksqldb-server:6.2.0 we have 1 topic where we push incoming events (topic-1) 1 Pull stream using "topic-1" as its source (stream-1) 1 Push stream CSAS (stream-2) that reads and transforms from the pull stream "stream-1" and pushes to "stream-2" topic We were working with this kind of setup for 1.5 years. The last migrations of the schemas was 1 month ago and yesterday, suddenly the persistent query writing to "stream-2" had zero consumers, even when restarting KSQL.
Any help would be greatly appreciated. Thank you.