Details
-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
1.1.0.Final
-
None
Description
My use case is continuous creating topics, creating connector, do some dev / testing work and deleting connector and topics. I do it multiple times a day while working on some streaming solution where Debezium is just the 1st layer (data ingestion). If I recreate the same setup again I get the following error:
org.apache.kafka.connect.errors.ConnectException: The db history topic is missing. You may attempt to recover it by reconfiguring the connector to SCHEMA_ONLY_RECOVERY at io.debezium.connector.mysql.MySqlConnectorTask.start(MySqlConnectorTask.java:103) at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:101) at org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:208) at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:177) at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:227) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)
If I use different connector name and topics it works.
I've just reproduced it in Debezium tutorial (Version 1.2). I went through all the steps till cleanup, deleted connector, schema and data topics and created the same connector again.
As I understand either Debezium lacks some cleanup on delete (or startup) or i miss some cleanup steps myself. Anyway the error itself is misleading. Because I do have that topic. I even tried to create it in advance.
