-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
-
False
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?
"class": "io.debezium.connector.db2as400.As400RpcConnector",
"type": "source",
"version": "3.0.4.Final"
What is the connector configuration?
{
"connector.class" : "io.debezium.connector.db2as400.As400RpcConnector",
"name" : "connector-name",
"sanitize.field.names" : "true",
"tasks.max" : "1",
"database.hostname" : "AS400",
"database.user" : "user",
"database.password" : "pw",
"database.port" : "8471",
"database.dbname" : "DB",
"database.schema" : "SCHEMA",
"driver.secure" : false,
"poll.interval.ms" : "5000",
"table.include.list" : "SCHEMA.TABLE",
"snapshot.mode" : "schema_only",
"key.converter.schema.registry.url" : "http://schema-registry.prod.com/",
"value.converter.schema.registry.url" : "http://schema-registry.prod.com/",
"key.converter" : "io.confluent.connect.avro.AvroConverter",
"value.converter" : "io.confluent.connect.avro.AvroConverter",
"socket timeout" : "300000",
"keep.alive" : "true",
"topic.prefix" : "db2.cdc",
"topic.creation.default.partitions" : 12,
"topic.creation.default.replication.factor" : 4,
"topic.creation.default.cleanup.policy" : "delete,compact",
"transforms" : "InsertField",
"transforms.InsertField.type" : "org.apache.kafka.connect.transforms.InsertField$Value",
"transforms.InsertField.static.field" : "event_source",
"transforms.InsertField.static.value" : "DB.SCHEMA.TABLE",
"max.journal.timeout" : "300000",
"header.converter": "org.apache.kafka.connect.storage.StringConverter",
"log4j.logger.io.debezium": "DEBUG",
"log4j.logger.org.apache.kafka": "DEBUG", }
What is the captured database version and mode of deployment?
7.4, on-premise
What behavior do you expect?
The Connector should capture all events from the Journal
What behavior do you see?
The Connector seems to randomly miss some journal entries. If the Connector is deployed twice with the same configuration (but different name), it manages to pick up the entry in one instance and not in the other one. We have tried running up to a 12 connectors at the same time pointing to the same journal/table but could not pinpoint what causes this behavior to occur. The journal entry type does not seem to effect if the event is picked up or not. We have also tried on a different table, but observed the same behavior. Behavior occurs on Journal mode BOTH as well as AFTER. We have set the log level to trace and debug for some Connectors, but could not see any error messages in the logs.
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
Not yet, but can get them if needed.
