Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
1.9.3.Final
-
None
-
False
-
None
-
False
-
Critical
Description
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:
What Debezium connector do you use and what version?
io.debezium.connector.sqlserver.SqlServerConnector and 1.9.3.Final
What is the connector configuration?
{
"name": "**************",
"config": {
"connector.class": "io.debezium.connector.sqlserver.SqlServerConnector",
"errors.log.include.messages": "true",
"topic.creation.default.partitions": "1",
"topic.creation.default.max.message.bytes": "8000000",
"database.history.consumer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"***********\" password=\"*************\";",
"database.history.kafka.topic": "dbhistory.************",
"confluent.topic.ssl.endpoint.identification.algorithm": "https",
"database.history.consumer.security.protocol": "SASL_SSL",
"database.history.kafka.recovery.attempts": "10",
"provide.transaction.metadata": "true",
"tombstones.on.delete": "false",
"topic.creation.default.replication.factor": "3",
"errors.log.enable": "true",
"database.history.producer.sasl.mechanism": "PLAIN",
"database.history.producer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"*******\" password=\"*****************\";",
"database.user": "************",
"database.dbname": "***********",
"topic.creation.default.compression.type": "snappy",
"confluent.topic.bootstrap.servers": "***********:9092",
"topic.creation.default.cleanup.policy": "delete",
"database.history.producer.security.protocol": "SASL_SSL",
"database.history.kafka.bootstrap.servers": "***************:9092",
"database.server.name": "***************",
"snapshot.isolation.mode": "read_committed",
"confluent.license.topic.replication.factor": "1",
"database.port": "1433",
"max.request.size": "2097164",
"producer.override.max.request.size": "8000000",
"database.hostname": "************",
"database.password": "***********",
"name": "**************",
"table.include.list": "****************",
"database.history.consumer.sasl.mechanism": "PLAIN",
"snapshot.mode": "initial",
"confluent.topic.request.timeout.ms": "20000"
},
"tasks": [
{
"connector": "*****************",
"task": 0
}
],
"type": "source"
}
What is the captured database version and mode of depoyment?
AWS SQL Server RDS Instance
What behaviour do you expect?
The connector to not fail
What behaviour do you see?
The connector fails randomly with below error
The update before event at 000db129:01cb1109:0007(000db129:01cb1109:0003) for table ****** was not followed by after event.\n Please report this as a bug together with a events around given LSN
Do you see the same behaviour using the latest relesead Debezium version?
We havent used the latest one as we are not understanding what the issue is.
Do you have the connector logs, ideally from start till finish?
No
How to reproduce the issue using our tutorial deployment?
The connector is currently running in production.
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
We are running this connector in produciton and we seem to be constantly running into this error and we have to restart constantly.
Implementation ideas (optional)
<Your answer>
