Issues with Debezium SQL Server Connector and KafkaSchemaHistory Configuration

Kafka Connect
1

Hello everyone,

I’m facing an issue while trying to configure the Debezium SQL Server Connector with Kafka. The connector is running, but the task is failing with the following error:
org.apache.kafka.connect.errors.ConnectException: Error configuring an instance of KafkaSchemaHistory; check the logs for details

I’ve already tried the following:

  1. Kafka Topics I checked if the topic schema-changes.mssql exists in Kafka. The topic exists, and I even created it manually using:
    kafka-topics.sh --create --bootstrap-server localhost:9092 --topic schema-changes.mssql --partitions 1 --replication-factor 1

  2. Kafka Broker: I confirmed that the Kafka broker is running and reachable. I successfully connected using `telnet localhost 9092

  3. Kafka Configuration: I’ve verified that the database.history.kafka.bootstrap.servers is correctly set to localhost:9092, and the database.history.kafka.topic is correctly configured.

  4. Internal History Topic: I added the internal history topic database.history.internal.kafka.topic as well to ensure the configuration is complete.

Here’s the current configuration I’m using:

{
“name”: “mssql-debezium-connector”,
“config”: {
“connector.class”: “io.debezium.connector.sqlserver.SqlServerConnector”,
“database.hostname”: “192.168.95.11”,
“database.user”: “my_user”,
“database.password”: “my_pass”,
“database.names”: “db_name”,
“topic.prefix”: “mssql-server”,
“database.server.name”: “mssql-server”,
“snapshot.mode”: “initial”,
“database.history.kafka.bootstrap.servers”: “localhost:9092”,
“database.history.kafka.topic”: “schema-changes.mssql”,
“database.history.internal.kafka.bootstrap.servers”: “localhost:9092”,
“database.history.internal.kafka.topic”: “schema-history-mssql”,
“database.trustServerCertificate”: “true”
}
}
I have also restarted the connector after applying these changes, but the error still persists.

Has anyone encountered this issue before or can point me to something I might be missing in the configuration? Any help would be greatly appreciated!

2

hey @Data_integrator

welcome :slight_smile:
any more details in the log around the error?

3

Hi
Thanks for the help! I already found the problem—instead of database.history, it should have been schema.history
Database.history is from an older version

1 Like