Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
1.9.0.Final
-
None
-
False
-
None
-
False
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?
version 1.9.0 for mysql
What is the connector configuration?
{
"name": "dbz-domain-list-09",
"config": {
"auto.create.topics": "false",
"connector.class": "io.debezium.connector.mysql.MySqlConnector",
"converters": "timestampConverter",
"database.history.consumer.sasl.jaas.config": "org.apache.kafka.common.security.scram.ScramLoginModule required username=\"${file:/app/data/cred/connector_credentials.properties:kuser}\" password=\"${file:/app/data/cred/connector_credentials.properties:kpassword}\";",
"database.history.consumer.sasl.mechanism": "SCRAM-SHA-512",
"database.history.consumer.security.protocol": "SASL_SSL",
"database.history.kafka.bootstrap.servers": "b-1:9096",
"database.history.kafka.topic": "dbhistory.list",
"database.history.producer.sasl.jaas.config": "org.apache.kafka.common.security.scram.ScramLoginModule required username=\"${file:/app/data/cred/connector_credentials.properties:kuser}\" password=\"${file:/app/data/cred/connector_credentials.properties:kpassword}\";",
"database.history.producer.sasl.mechanism": "SCRAM-SHA-512",
"database.history.producer.security.protocol": "SASL_SSL",
"database.hostname": "value",
"database.include.list": "list",
"database.password": "${file:/app/data/cred/connector_credentials.properties:mypwd}",
"database.port": "3306",
"database.server.name": "lstrp-list",
"database.user": "${file:/app/data/cred/connector_credentials.properties:myuser}",
"decimal.handling.mode": "double",
"errors.log.enable": "true",
"errors.log.include.messages": "true",
"errors.tolerance": "all",
"include.schema.changes": "false",
"message.key.columns": "list.lr_list_item:list_id",
"signal.data.collection": "list.debezium_signal",
"snapshot.locking.mode": "none",
"snapshot.mode": "initial",
"table.include.list": "list.debezium_signal,list.lr_list",
"tasks.max": "1",
"timestampConverter.format.datetime": "YYYY-MM-dd'T'HH:mm:ss.SSS'Z'",
"timestampConverter.type": "oryanmoshe.kafka.connect.util.TimestampConverter",
"transforms.Reroute.key.enforce.uniqueness": "false",
"transforms.Reroute.topic.regex": "(.*)",
"transforms.Reroute.topic.replacement": "list-cdc-lists-02",
"transforms.Reroute.type": "io.debezium.transforms.ByLogicalTableRouter",
"transforms": "Reroute"
}
What is the captured database version and mode of depoyment?
aws rds mysql version 5.7.25
What behaviour do you expect?
See the debezium jmx metric to be in a positive number
What behaviour do you see?
I see the mysql debezium jmx metric in a negative number after changing ec2 instance to be CDT to match the mysql timezone.
Do you see the same behaviour using the latest relesead Debezium version?
this is issue is from version 1.9.0
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?
<Your answer>
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>