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

Debezium server doesn't recognize 'execute-snaphot' signal

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 3.0.0.Final
    • debezium-server
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Important

      Bug report

      What Debezium connector do you use and what version?

      Debezium Server 3.0.0.Final, using SQLServer connector.

      What is the connector configuration?

       

      quarkus.log.console.enable=true
      quarkus.log.file.enable=true
      quarkus.log.file.json=true
      quarkus.log.file.path=logs/application.log
      quarkus.log.file.format=%d{yyyy-MM-dd HH:mm:ss} %-5p [%c] (%t) %s%e%n
      quarkus.log.level=TRACE
      debezium.source.database.hostname=sqlserver
      debezium.source.database.port=1433
      debezium.source.database.user=sa
      debezium.source.database.password=Password!
      debezium.source.database.encrypt=false
      debezium.source.database.names=testdb,config
      debezium.source.table.include.list=dbo.customers,dbo.debezium_signal
      debezium.source.connector.class=io.debezium.connector.sqlserver.SqlServerConnector
      debezium.source.offset.storage=org.apache.kafka.connect.storage.FileOffsetBackingStore
      debezium.source.offset.storage.file.filename=/opt/debezium-server/data/offsets.dat
      debezium.source.offset.flush.interval.ms=0
      debezium.source.schema.history.internal=io.debezium.storage.file.history.FileSchemaHistory
      debezium.source.schema.history.internal.file.filename=/opt/debezium-server/data/history.dat
      debezium.source.snapshot.mode=no_data
      debezium.source.topic.prefix=sqlserver
      debezium.source.value.converter.schemas.enable=false
      debezium.source.include.schema.changes=false
      debezium.source.signal.data.collection=config.dbo.debezium_signal
      debezium.source.signal.enabled.channels=source
      
      debezium.sink.type=kafka
      debezium.sink.kafka.producer.bootstrap.servers=kafka:9092
      debezium.sink.kafka.producer.key.serializer=org.apache.kafka.common.serialization.StringSerializer
      debezium.sink.kafka.producer.value.serializer=org.apache.kafka.common.serialization.StringSerializer 

       

       

      What is the captured database version and mode of deployment?

      SQLServer 2019 on docker container

      What behavior do you expect?

      When inserting signal 'execute-snapshot' in the signal table the snapshot is performed.

      What behavior do you see?

      {"timestamp":"2025-03-06T15:36:09.092330966Z","sequence":29982,"loggerClassName":"org.slf4j.impl.Slf4jLogger","loggerName":"io.debezium.pipeline.signal.SignalProcessor","level":"WARN","message":"Signal '12345' has been received but the type 'execute-snapshot' is not recognized","threadName":"debezium-sqlserverconnector-mailup_sqlservername-change-event-source-coordinator","threadId":48,"mdc":{"dbz.taskId":"0","dbz.databaseName":"config","dbz.connectorName":"mailup_sqlservername","dbz.connectorType":"SQL_Server","dbz.connectorContext":"streaming"},"ndc":"","hostName":"c6017e17e407","processName":"io.debezium.server.Main","processId":1}
      

      It seems that the seignal type is not correctly recognized.

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

      Yes

       

              Unassigned Unassigned
              marcore94 Marco Re (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: