Debezium: The db history topic or its content is fully or partially missing. Please check database history topic configuration and re-execute the snapshot

Been struggling with this issue for weeks now. Long story short, we try to create a Debezium connector and for various reasons it might fail. This creates an issue when trying to recreate the connector. Subsequent recreates fail with the following exception: The db history topic or its content is fully or partially missing. Please check database history topic configuration and re-execute the snapshot. and we have NOT found a way around this except to recreate the connector with a different name which is NOT what we want to do.

We are thinking the issue is during the first connector creation, an internal offset is stored somewhere and linked to that connector name but the issue is there is no way to clear or delete this. I have seen where if we wait 7 days maybe it eventually gets purged or cleared but we can’t work like this…we need a way to re-configure, delete and re-add, update…something to resolve this connector issue, even if it means deleting the history topic and starting over.

1 Like

Yup. I encountered exactly the same problem when trying out debezium to see if we would use it in production.

A work around is to change the name of the connector and that works but not an elegant resolution. The issue is that when a connector is deleted, the history topic remains and is now out of sync.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.