Open konstan opened 3 years ago
Update: the instance of ksqldb was running fine for about 9 hours and then the problem described above happened again.
I met with same problem when I want to drop a stream with query to it , even not use PARTITION BY
,even when drop a table
,it also throws exception:io.confluent.ksql.query.QueryId cannot be cast to java.lang.Comparable
Describe the bug
The stream that re-keys another one using PARTITION BY, stops producing results after running for some time. The queries that read from that stream receive no results.
To Reproduce Steps to reproduce the behavior, include:
KSQL - 0.15.0 image
confluentinc/ksqldb-server:0.15.0
The ksql statements are defined here https://github.com/nuvla/deployment/blob/master/streams/ksqldb/statements.replicas-1.sql#L273 and
CREATE STREAM NB_TELEM_RESOURCES_REKYED_S
is the one that stops working. The FROM stream, the failing one rekeys, works with no problems.Expected behavior
The stream should be working.
Actual behaviour
The stream stops working after some time.
Attempting to query the stream from ksql shell produces no results.
Here is one of the many such warnings in
ksql-streams.log
.CSAS_NB_TELEM_RESOURCES_REKYED_S_637
is the querey that writes from the stream re-keying stream that stops working.Restarting ksqldb doesn't help.
Dropping the stream directly returns the error below, while I was expecting a suggestion with lists of source/sink queries to terminate.
Heres are the logs from the ksqldb instance. ksqldb.logs.tgz.zip Please remove
.zip
extension and unpackksqldb.logs.tgz
. I'm new to ksqldb and don't know how to interpret the logs. So, I can not tell exactly when the problem appears. The logs span the time from when the stream was working fine and then at some point stopped producing results.Here is the extended description of the stream.