In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

We are using Debezium V 2.5, and getting below error on successfully deployed Connector when KC instance goes down. and It does not start even after Restart of Task/Connector.

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

What Debezium connector do you use and what version?

Debezium V 2.5.4.Final

What is the connector configuration?

{
"name": "oee-2",
    "config":

{ "connector.class": "io.debezium.connector.sqlserver.SqlServerConnector", "driver.encrypt": "false", "database.user": "eam_ignitionUser", "database.names": "<DBNAME>", "database.dbname":  "<DBNAME>", "tasks.max": "1", "database.history.kafka.bootstrap.servers": "<KafkaZKBorkers>", "producer.bootstrap.servers": "<KafkaZKBorkers>", "producer.security.protocol" : "SASL_SSL", "producer.sasl.jaas.config": "<JAAS_CONIG>", "producer.sasl.mechanism" : "SCRAM-SHA-256", "producer.ssl.truststore.type":"PEM", "producer.ssl.truststore.location":"<CA_CERT_PATH>", "database.history.kafka.topic": "oee-1.history", "database.server.name": "INST2", "database.port": "1434", "value.converter.schema.registry.url": "<SR_URL>", "topic.prefix": "oee-2", "connect.protocol": "eager", "database.hostname": "<DB_HOSTNAME>", "database.password": "<DB_PWD>", "value.converter.schemas.enable": "true",  "database.trustServerCertificate": "false", "table.include.list": "<DB_TABLE_LIST>", "database.include.list": "<DB>", "schema.history.internal": "io.debezium.storage.file.history.FileSchemaHistory", "schema.history.internal.file.filename":"/security/schistory.dat" }

}

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

On prem. MSSQL 

What behaviour do you expect?

Connector should restart/resume its task after KafkaCOnnect pod/instance re-instantiated. and resume event streaming  .

What behaviour do you see?

Getting below error on successfully deployed Connector when KC instance goes down. and It does not start even after Restart of Task/Connector.

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

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

We are using pretty new Version Debezium V2.5.4.Final

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

How to reproduce the issue using our tutorial deployment?

• Deploy Kafka Connect.
• Create Connector (succesfully, streaming/snapshot happends)
• Delete Pod/instance of Kafka Connect
• You will see Connector in Failed state

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>