Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-1410

Error processing RDS heartbeats

    Details

      Description

      After upgrading too 0.10.0.Beta2, this error message starts to show up. Im very sure that the bingo format is set to ROW. I'll try the `event.deserialization​.failure.handling.mode = warn` option later.

      Jul 19, 2019 4:15:12 AM com.github.shyiko.mysql.binlog.BinaryLogClient connect
      INFO: Connected to toreta-rails:3307 at mysql-bin-changelog.020309/521 (sid:6283, cid:21359)
      19-07-19 04:15:12 cdc-extractor-844f85d477-rnf6c INFO [cdc-extractor.engine:53] - Task stopped.
      19-07-19 04:15:12 cdc-extractor-844f85d477-rnf6c INFO [cdc-extractor.engine:51] - Connector stopped.
      19-07-19 04:15:12 cdc-extractor-844f85d477-rnf6c ERROR [cdc-extractor.engine:59] - Connector completed with error: org.apache.kafka.connect.errors.ConnectException: Received DML 'INSERT INTO mysql.rds_heartbeat2(id, value) values (1,1563509488655) ON DUPLICATE KEY UPDATE value = 1563509488655' for processing, binlog probably contains events generated with statement or mixed based replication format
      #error {
       :cause Received DML 'INSERT INTO mysql.rds_heartbeat2(id, value) values (1,1563509488655) ON DUPLICATE KEY UPDATE value = 1563509488655' for processing, binlog probably contains events generated with statement or mixed based replication format
       :via
       [{:type org.apache.kafka.connect.errors.ConnectException
         :message Received DML 'INSERT INTO mysql.rds_heartbeat2(id, value) values (1,1563509488655) ON DUPLICATE KEY UPDATE value = 1563509488655' for processing, binlog probably contains events generated with statement or mixed based replication format
         :at [io.debezium.connector.mysql.AbstractReader wrap AbstractReader.java 230]}
        {:type org.apache.kafka.connect.errors.ConnectException
         :message Received DML 'INSERT INTO mysql.rds_heartbeat2(id, value) values (1,1563509488655) ON DUPLICATE KEY UPDATE value = 1563509488655' for processing, binlog probably contains events generated with statement or mixed based replication format
         :at [io.debezium.connector.mysql.BinlogReader handleQueryEvent BinlogReader.java 698]}]
       :trace
       [[io.debezium.connector.mysql.BinlogReader handleQueryEvent BinlogReader.java 698]
        [io.debezium.connector.mysql.BinlogReader handleEvent BinlogReader.java 501]
        [com.github.shyiko.mysql.binlog.BinaryLogClient notifyEventListeners BinaryLogClient.java 1095]
        [com.github.shyiko.mysql.binlog.BinaryLogClient listenForEventPackets BinaryLogClient.java 943]
        [com.github.shyiko.mysql.binlog.BinaryLogClient connect BinaryLogClient.java 580]
        [com.github.shyiko.mysql.binlog.BinaryLogClient$7 run BinaryLogClient.java 825]
        [java.lang.Thread run Thread.java 748]]}
      

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jpechanec Jiri Pechanec
                Reporter:
                haokang.den Haokang Den
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: