canal+kafka部署安装及问题解决

[canal]canal+kafka部署安装及问题解决

canal部署

canal 官网 https://github.com/alibaba/canal。

一、MySql开启binlog日志

找到my.cnf文件,并进行编辑

vim /usr/my.cnf

增加my.cnf配置

[mysqld]
#开启binlog
log-bin=mysql-bin
# binlog格式
# 1. STATEMENT：基于SQL语句的模式，binlog 数据量小，但是某些语句和函数在复制过程可能导致数据不一致甚至出错；
# 2. MIXED：混合模式，根据语句来选用是 STATEMENT 还是 ROW 模式；
# 3. ROW：基于行的模式，记录的是行的完整变化。安全，但 binlog 会比其他两种模式大很多；
binlog-format=ROW
#给当前mysql一个server id，同一局域网内注意要唯一，这里一定要填，有些数据库没有配置
server_id=1
# FULL：binlog记录每一行的完整变更 MINIMAL：只记录影响后的行
binlog_row_image=FULL
...省略其他无关配置...注意：编码一定要一样
————————————————
版权声明：本文为CSDN博主「奋笔疾书xrp」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。
原文链接：https://blog.csdn.net/xu963981912/article/details/131090988

开启binlog之后重启mysql服务:

#重启mysql服务
service mysqld restart
#查看mysql服务状态
service mysqld status

进入mysql命令行，使用下面的命令查看binlog开启的情况：

mysql> show variables like 'log_bin';
mysql> show variables like 'binlog_format';

二、安装Canal Server

上传canal.deployer-1.1.4.tar.gz到指定文件夹，并进行解压

tar -zxvf canal.deployer-1.1.4.tar.gz -C canal

进入canal/conf文件夹下，修改配置文件

vim canal.properties

#################################################
######### 		common argument		#############
#################################################
# tcp bind ip
canal.ip =
# register ip to zookeeper
canal.register.ip =
canal.port = 11111
canal.metrics.pull.port = 11112
# canal instance user/passwd
# canal.user = canal
# canal.passwd = E3619321C1A937C46A0D8BD1DAC39F93B27D4458

# canal admin config
#canal.admin.manager = 127.0.0.1:8089
canal.admin.port = 11110
canal.admin.user = admin
canal.admin.passwd = 4ACFE3202A5FF5CF467898FC58AAB1D615029441

canal.zkServers = 172.32.1.174:2181
# flush data to zk
canal.zookeeper.flush.period = 1000
canal.withoutNetty = false
# tcp, kafka, RocketMQ
canal.serverMode = kafka
# flush meta cursor/parse position to file
canal.file.data.dir = ${canal.conf.dir}
canal.file.flush.period = 1000
## memory store RingBuffer size, should be Math.pow(2,n)
canal.instance.memory.buffer.size = 16384
## memory store RingBuffer used memory unit size , default 1kb
canal.instance.memory.buffer.memunit = 1024 
## meory store gets mode used MEMSIZE or ITEMSIZE
canal.instance.memory.batch.mode = MEMSIZE
canal.instance.memory.rawEntry = true

## detecing config
canal.instance.detecting.enable = false
#canal.instance.detecting.sql = insert into retl.xdual values(1,now()) on duplicate key update x=now()
canal.instance.detecting.sql = select 1
canal.instance.detecting.interval.time = 3
canal.instance.detecting.retry.threshold = 3
canal.instance.detecting.heartbeatHaEnable = false

# support maximum transaction size, more than the size of the transaction will be cut into multiple transactions delivery
canal.instance.transaction.size =  1024
# mysql fallback connected to new master should fallback times
canal.instance.fallbackIntervalInSeconds = 60

# network config
canal.instance.network.receiveBufferSize = 16384
canal.instance.network.sendBufferSize = 16384
canal.instance.network.soTimeout = 30

# binlog filter config
canal.instance.filter.druid.ddl = true
canal.instance.filter.query.dcl = false
canal.instance.filter.query.dml = false
canal.instance.filter.query.ddl = false
canal.instance.filter.table.error = false
canal.instance.filter.rows = false
canal.instance.filter.transaction.entry = false

# binlog format/image check
canal.instance.binlog.format = ROW,STATEMENT,MIXED 
canal.instance.binlog.image = FULL,MINIMAL,NOBLOB

# binlog ddl isolation
canal.instance.get.ddl.isolation = false

# parallel parser config
canal.instance.parser.parallel = true
## concurrent thread number, default 60% available processors, suggest not to exceed Runtime.getRuntime().availableProcessors()
#canal.instance.parser.parallelThreadSize = 16
## disruptor ringbuffer size, must be power of 2
canal.instance.parser.parallelBufferSize = 256

# table meta tsdb info
canal.instance.tsdb.enable = true
canal.instance.tsdb.dir = ${canal.file.data.dir:../conf}/${canal.instance.destination:}
canal.instance.tsdb.url = jdbc:h2:${canal.instance.tsdb.dir}/h2;CACHE_SIZE=1000;MODE=MYSQL;
canal.instance.tsdb.dbUsername = canal
canal.instance.tsdb.dbPassword = canal
# dump snapshot interval, default 24 hour
canal.instance.tsdb.snapshot.interval = 24
# purge snapshot expire , default 360 hour(15 days)
canal.instance.tsdb.snapshot.expire = 360

# aliyun ak/sk , support rds/mq
canal.aliyun.accessKey =
canal.aliyun.secretKey =

#################################################
######### 		destinations		#############
#################################################
canal.destinations = example
# conf root dir
canal.conf.dir = ../conf
# auto scan instance dir add/remove and start/stop instance
canal.auto.scan = true
canal.auto.scan.interval = 5

canal.instance.tsdb.spring.xml = classpath:spring/tsdb/h2-tsdb.xml
#canal.instance.tsdb.spring.xml = classpath:spring/tsdb/mysql-tsdb.xml

canal.instance.global.mode = spring
canal.instance.global.lazy = false
canal.instance.global.manager.address = ${canal.admin.manager}
#canal.instance.global.spring.xml = classpath:spring/memory-instance.xml
canal.instance.global.spring.xml = classpath:spring/file-instance.xml
#canal.instance.global.spring.xml = classpath:spring/default-instance.xml

##################################################
######### 		     MQ 		     #############
##################################################
canal.mq.servers = xxx:9092,xxx:9092,xxx:9092
canal.mq.retries = 0
canal.mq.batchSize = 16384
canal.mq.maxRequestSize = 1048576
canal.mq.lingerMs = 100
canal.mq.bufferMemory = 33554432
canal.mq.canalBatchSize = 50
canal.mq.canalGetTimeout = 100
canal.mq.flatMessage = true
canal.mq.compressionType = none
canal.mq.acks = all
#canal.mq.properties. =
canal.mq.producerGroup = test
# Set this value to "cloud", if you want open message trace feature in aliyun.
canal.mq.accessChannel = local
# aliyun mq namespace
#canal.mq.namespace =

##################################################
#########     Kafka Kerberos Info    #############
##################################################
kafka.bootstrap.servers = xxx:9092,xxx:9092,xxx:9092
kafka.acks = all
kafka.compression.type = none
kafka.batch.size = 16384
kafka.linger.ms = 1
kafka.max.request.size = 1048576
kafka.buffer.memory = 33554432
kafka.max.in.flight.requests.per.connection = 1
kafka.retries = 0

canal.mq.kafka.kerberos.enable = false
canal.mq.kafka.kerberos.krb5FilePath = "../conf/kerberos/krb5.conf"
canal.mq.kafka.kerberos.jaasFilePath = "../conf/kerberos/jaas.conf"

需要修改的配置项为：

canal.serverMode = kafka
canal.mq.servers = xxx:9092,xxx:9092,xxx:9092
canal.destinations = example

配置监听的数据库，修改conf/example/instance.properties，主要修改监听的数据库，以及topic的策略

#################################################
## mysql serverId , v1.0.26+ will autoGen
# canal.instance.mysql.slaveId=0

# enable gtid use true/false
canal.instance.gtidon=false

# position info  修改为自己要监听的数据库
canal.instance.master.address=xxx:3367
canal.instance.master.journal.name=
canal.instance.master.position=
canal.instance.master.timestamp=
canal.instance.master.gtid=

# rds oss binlog
canal.instance.rds.accesskey=
canal.instance.rds.secretkey=
canal.instance.rds.instanceId=

# table meta tsdb info
canal.instance.tsdb.enable=true
#canal.instance.tsdb.url=jdbc:mysql://127.0.0.1:3306/canal_tsdb
#canal.instance.tsdb.dbUsername=canal
#canal.instance.tsdb.dbPassword=canal

#canal.instance.standby.address =
#canal.instance.standby.journal.name =
#canal.instance.standby.position =
#canal.instance.standby.timestamp =
#canal.instance.standby.gtid=

# username/password  修改用户名密码
canal.instance.dbUsername=canal
canal.instance.dbPassword=1canal
canal.instance.connectionCharset = UTF-8
# enable druid Decrypt database password
canal.instance.enableDruid=false
#canal.instance.pwdPublicKey=MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALK4BUxdDltRRE5/zXpVEVPUgunvscYFtEip3pmLlhrWpacX7y7GCMo2/JM6LeHmiiNdH1FWgGCpUfircSwlWKUCAwEAAQ==

# table regex  监听表的过滤
canal.instance.filter.regex=
# table black regex
canal.instance.filter.black.regex=
# table field filter(format: schema1.tableName1:field1/field2,schema2.tableName2:field1/field2)
#canal.instance.filter.field=test1.t_product:id/subject/keywords,test2.t_company:id/name/contact/ch
# table field black filter(format: schema1.tableName1:field1/field2,schema2.tableName2:field1/field2)
#canal.instance.filter.black.field=test1.t_product:subject/product_image,test2.t_company:id/name/contact/ch

# mq config  kafka的topic
canal.mq.topic=canal_test
# dynamic topic route by schema or table regex
#canal.mq.dynamicTopic=mytest1.user,mytest2\\..*,.*\\..*
canal.mq.partition=0
# hash partition config
#canal.mq.partitionsNum=3
#canal.mq.partitionHash=test.table:id^name,.*\\..*
#################################################

canal支持MQ数据的几种路由方式：单topic单分区，单topic多分区、多topic单分区、多topic多分区
重点来了: 其中我们主要关注创建topic的方式，是固定是还是按照一个表一个topic，还是一个库一个topic，以及topic的分区信息。
如果要保证消息的顺序，那么至少是一个库的所有表只往一个topic的单分区写。 或者一个表只往一个topic的单分区写。不然就会出现问题。

三、启动canal

sh bin/startup.sh

参看日志：

tail -200f logs/canal/canal.log          #查看canal服务日志
tail -200f logs/example/example.log

四、数据验证

这个步骤很简单，不管是客户端还是写个程序，只需要往监听的表里插入一条数据即可，启动一个kafka客户端，看是否接受到消息。

./kafka-console-consumer.sh  --bootstrap-server xxxx:9092,xxxx:9092,xxxx:9092 --topic test --from-beginning

可以看到有数据返回：

{"data":[{"id":"2282","collect_hist_id":null,"data_source_id":null,"type":"column","tid":"15","name":"ttt","cn_name":"ttt","pid":"2273","schema_meta_id":"2272","db_type":null,"create_time":null,"update_time":null,"del":"0","data_rule_id":null,"data_rule_name":null,"pids":null}],"database":"xgov-0104","es":1689130854000,"id":4,"isDdl":false,"mysqlType":{"id":"bigint(20)","collect_hist_id":"int(11)","data_source_id":"int(11)","type":"varchar(100)","tid":"int(11)","name":"varchar(255)","cn_name":"varchar(255)","pid":"bigint(20)","schema_meta_id":"bigint(20)","db_type":"varchar(50)","create_time":"datetime","update_time":"datetime","del":"varchar(1)","data_rule_id":"bigint(20)","data_rule_name":"varchar(255)","pids":"varchar(100)"},"old":[{"tid":null,"name":null,"cn_name":null,"pid":null,"schema_meta_id":null}],"pkNames":["id"],"sql":"","sqlType":{"id":-5,"collect_hist_id":4,"data_source_id":4,"type":12,"tid":4,"name":12,"cn_name":12,"pid":-5,"schema_meta_id":-5,"db_type":12,"create_time":93,"update_time":93,"del":12,"data_rule_id":-5,"data_rule_name":12,"pids":12},"table":"md_base_metadata","ts":1689130857141,"type":"UPDATE"}
{"data":[{"id":"2282","collect_hist_id":null,"data_source_id":null,"type":"column","tid":"15","name":"ttt","cn_name":"ttt","pid":"2273","schema_meta_id":"2272","db_type":null,"create_time":null,"update_time":null,"del":"0","data_rule_id":null,"data_rule_name":null,"pids":null}],"database":"xgov-0104","es":1689141497000,"id":1347,"isDdl":false,"mysqlType":{"id":"bigint(20)","collect_hist_id":"int(11)","data_source_id":"int(11)","type":"varchar(100)","tid":"int(11)","name":"varchar(255)","cn_name":"varchar(255)","pid":"bigint(20)","schema_meta_id":"bigint(20)","db_type":"varchar(50)","create_time":"datetime","update_time":"datetime","del":"varchar(1)","data_rule_id":"bigint(20)","data_rule_name":"varchar(255)","pids":"varchar(100)"},"old":null,"pkNames":["id"],"sql":"","sqlType":{"id":-5,"collect_hist_id":4,"data_source_id":4,"type":12,"tid":4,"name":12,"cn_name":12,"pid":-5,"schema_meta_id":-5,"db_type":12,"create_time":93,"update_time":93,"del":12,"data_rule_id":-5,"data_rule_name":12,"pids":12},"table":"md_base_metadata","ts":1689141499713,"type":"DELETE"}

问题记录

链接: link.
启动后canal报错连不上kafka生产者：

2023-07-12 10:56:49.268 [kafka-producer-network-thread | producer-1] WARN  org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Connection to node -1 could not be established. Broker may not be available.

example实例也一直报错：

org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.

后来才发现是一开始我在canal.properties的配置中，将kafka的连接信息配置在了：

kafka.bootstrap.servers = xxx:9092,xxx:9092,xxx:9092

这是我看的其他博主描述部署时的修改参数，后来才发现1.1.4版本中是需要配置在这个属性中：

canal.mq.servers = xxx:9092,xxx:9092,xxx:9092

修改后解决了该问题。