我按照此示例将数据从 mysql 流式传输到 elasticsearch https://github.com/debezium/debezium-examples/tree/master/unwrap-smt#elasticsearch-sink 该示例本身在我的本地机器上运行良好。
但就我而言,我想将数据从 mssql(在另一台服务器上,而不是 docker 上)流式传输到 elasticsearch。
因此,在“docker-compose-es.yaml”文件中,我删除了“mysql”部分并删除了 mysql 链接。 并为弹性和 mssql 创建了我自己的连接器/接收器:
{
"name": "Test-connector",
"config": {
"connector.class": "io.debezium.connector.sqlserver.SqlServerConnector",
"database.hostname": "192.168.1.234",
"database.port": "1433",
"database.user": "user",
"database.password": "pass",
"database.dbname": "Test",
"database.server.name": "MyServer",
"table.include.list": "dbo.TEST_A",
"database.history.kafka.bootstrap.servers": "kafka:9092",
"database.history.kafka.topic": "dbhistory.testA"
}
}
{
"name": "elastic-sink-test",
"config": {
"connector.class": "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector",
"tasks.max": "1",
"topics": "TEST_A",
"connection.url": "http://localhost:9200/",
"transforms": "unwrap,key",
"transforms.unwrap.type": "io.debezium.transforms.UnwrapFromEnvelope",
"transforms.unwrap.drop.tombstones": "false",
"transforms.key.type": "org.apache.kafka.connect.transforms.ExtractField$Key",
"transforms.key.field": "SQ",
"key.ignore": "false",
"type.name": "TEST_A",
"behavior.on.null.values": "delete"
}
}
当添加这些时,kafka connect I/O 正在努力工作并且有超过 40GB 的输入,见下图:
在 kafka 日志中,它看起来像是遍历了所有表。这是表日志之一:
2021-06-17 10:20:10,414 - INFO [data-plane-kafka-request-handler-5:Logging@66] - [Partition MyServer.dbo.TemplateGroup-0 broker=1] Log loaded for partition MyServer.dbo.TemplateGroup-0 with initial high watermark 0
2021-06-17 10:20:10,509 - INFO [data-plane-kafka-request-handler-3:Logging@66] - Creating topic MyServer.dbo.TemplateMeter with configuration {} and initial partition assignment Map(0 -> ArrayBuffer(1))
2021-06-17 10:20:10,516 - INFO [data-plane-kafka-request-handler-3:Logging@66] - [KafkaApi-1] Auto creation of topic MyServer.dbo.TemplateMeter with 1 partitions and replication factor 1 is successful
2021-06-17 10:20:10,526 - INFO [data-plane-kafka-request-handler-7:Logging@66] - [ReplicaFetcherManager on broker 1] Removed fetcher for partitions Set(MyServer.dbo.TemplateMeter-0)
2021-06-17 10:20:10,528 - INFO [data-plane-kafka-request-handler-7:Logging@66] - [Log partition=MyServer.dbo.TemplateMeter-0, dir=/kafka/data/1] Loading producer state till offset 0 with message format version 2
数据库只有 2GB。我不知道为什么它有这么高的投入。
运行此命令时,elasticsearch 中未创建 test_a 索引:
curl http://localhost:9200/_aliases?pretty=true
有谁知道我如何从这里进行故障排除或为我指明正确的方向?
提前致谢!
答案 0 :(得分:0)
我如何从这里进行故障排除
docker compose logs
?
修改 Kafka Connect 和/或 Elasitcsearch 进程的 log4j.properties 以获得更多日志?
使用普通的 Kafka 消费者查看数据是否真正读入 TEST_A
主题?
在“docker-compose-es.yaml”中....
如果 Debezium 在容器中运行,那么 Elasticsearch 在 localhost:9200 处不可用
将该值更改为 http://elastic:9200
, like shown in the es-sink.json