canal+mysql+kafka[windows环境搭建]

最新推荐文章于 2024-04-27 10:14:14 发布

qq_42174979

最新推荐文章于 2024-04-27 10:14:14 发布

阅读量696

点赞数

文章标签： kafka mysql 分布式

本文链接：https://blog.csdn.net/qq_42174979/article/details/124703955

版权

针对公司资源环境申请都要走流程，麻烦死，故在本地搭建一套用于自测。

1.zookeeper

官网下载：Apache ZooKeeper

这里用的是 apache-zookeeper-3.6.3-bin

zk配置修改:

windows下启动记得把路径 apache-zookeeper-3.6.3-bin\conf里面的zoo_sample.cfg文件复制一份，改名为zoo.cfg

2.运行bin目录下的zkServer.cmd

【注：如果点击就闪退，可以在脚本最后加入pause来查看错误信息，如下图】

2.kafka

官网下载：Apache Kafka

这里用的版本是 kafka_2.12-2.8.1

【注：开始下的新版kafka_2.12-3.0.0，然后windows启动会遇到问题，参考博客降低版本解决： KAFKA - ERROR Failed to write meta.properties due to (kafka.server.BrokerMetadataCheckpoint)_从一而终的博客-CSDN博客】

kafka配置修改:

此处未修改端口等配置，均为默认，故不涉及kafka配置文件修改
启动：在 kafka_2.12-2.8.1\bin\windows目录下，打开cmd窗口，运行命令：

kafka-server-start.bat ../../config/server.properties

3.开启一个黑窗口，创建一个topic：在 kafka_2.12-2.8.1\bin\windows目录下，打开cmd窗口，运行命令【后续用canal往这个topic发送消息，此处topic名为：canaltopic】：

kafka-topics.bat --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic canaltopic

4.开启一个黑窗口，运行监听topic命令【来监听这个topic】：

kafka-console-consumer.bat --bootstrap-server 127.0.0.1:9092 --from-beginning --topic canaltopic

3.canal

官网下载：https://github.com/alibaba/canal/releases

这里用的版本是 canal.deployer-1.1.4

canal配置修改：

1.canal.deployer-1.1.4/conf目录下的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 =
# 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       #############
#################################################

# 配置instance，在conf目录下要有example同名的目录，可以配置多个
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        #############
##################################################

# 配置MQ的服务地址，这里配置的是kafka对应的地址和端口
canal.mq.servers = 127.0.0.1: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 #############
##################################################
canal.mq.kafka.kerberos.enable = false
canal.mq.kafka.kerberos.krb5FilePath = "../conf/kerberos/krb5.conf"
canal.mq.kafka.kerberos.jaasFilePath = "../conf/kerberos/jaas.conf"

2./conf/example/instance.properties配置文件：

#################################################
## 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=127.0.0.1:3306

# 在Mysql执行 SHOW MASTER STATUS;查看当前数据库的binlog
canal.instance.master.journal.name=LAPTOP-HO7QT2DV-bin.000006
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=root
canal.instance.dbPassword=passw
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
canal.mq.topic=canaltopic
# 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,.*\\..*
#################################################

4.binglog不通模式下canal的消息体格式：

binlog有3中模式，ROW（行模式）, Statement（语句模式）, Mixed（混合模式）三种模式的用法如下：　ROW（行模式）：记录那条数据修改了，注意：记录的是这条记录的全部数据，即使只更新了一个字段，binlog里也会记录所有字段的数据优点：他不记录sql语句的上下文信息，日志内容会非常清楚的记录每条数据详细的变更细节，即使只更新了一个字段，binlog里也会记录所有字段的数据。缺点：binlog日志会非常大，mysql主从同步时，会产生大量磁盘IO

Statement（语句模式）: 每一条会修改数据的sql都会记录在binlog中。优点：不需要记录每一行的变化，减少了binlog日志量，节约了IO，提高性能。缺点：由于记录的只是执行语句，为了这些语句能在slave上正确运行，因此还必须记录每条语句在执行的时候的一些相关信息，以保证所有语句能在slave得到和在master端执行时候相同的结果。另外mysql 的复制,像一些特定函数功能，slave可与master上要保持一致会有很多相关问题。

Mixed（混合模式）：在Mixed模式下，一般的语句修改使用statment格式保存binlog，如一些函数，statement无法完成主从复制的操作，则采用row格式保存binlog，MySQL会根据执行的每一条具体的sql语句来区分对待记录的日志形式，也就是在Statement和Row之间选择一种。

你有可能模式选的ROW，导致只有数据变化，没有sql语句

# row模式下的消息体

#insert消息体
{"data":[{"stratum_id":"10004","stratum_name":"监控中心","deep":"2","publish_portal":"8","rank":"2","remark":null,"own_sys":null,"is_root":"0","create_time":null,"creater":null,"update_time":null,"updater":null}],"database":"sys","es":1652168288000,"id":2,"isDdl":false,"mysqlType":{"stratum_id":"bigint(20)","stratum_name":"varchar(100)","deep":"int(2)","publish_portal":"varchar(32)","rank":"int(3)","remark":"varchar(500)","own_sys":"varchar(2)","is_root":"char(1)","create_time":"datetime","creater":"varchar(100)","update_time":"datetime","updater":"varchar(100)"},"old":null,"pkNames":["stratum_id"],"sql":"","sqlType":{"stratum_id":-5,"stratum_name":12,"deep":4,"publish_portal":12,"rank":4,"remark":12,"own_sys":12,"is_root":1,"create_time":93,"creater":12,"update_time":93,"updater":12},"table":"auth_stratum","ts":1652168288145,"type":"INSERT"}
#delete消息体

{"data":[{"stratum_id":"10004","stratum_name":"监控中心","deep":"2","publish_portal":"8","rank":"2","remark":null,"own_sys":null,"is_root":"0","create_time":null,"creater":null,"update_time":null,"updater":null}],"database":"sys","es":1652168630000,"id":3,"isDdl":false,"mysqlType":{"stratum_id":"bigint(20)","stratum_name":"varchar(100)","deep":"int(2)","publish_portal":"varchar(32)","rank":"int(3)","remark":"varchar(500)","own_sys":"varchar(2)","is_root":"char(1)","create_time":"datetime","creater":"varchar(100)","update_time":"datetime","updater":"varchar(100)"},"old":null,"pkNames":["stratum_id"],"sql":"","sqlType":{"stratum_id":-5,"stratum_name":12,"deep":4,"publish_portal":12,"rank":4,"remark":12,"own_sys":12,"is_root":1,"create_time":93,"creater":12,"update_time":93,"updater":12},"table":"auth_stratum","ts":1652168630830,"type":"DELETE"}

#update消息体

{"data":[{"stratum_id":"10002","stratum_name":"监控中心2","deep":"3","publish_portal":"8","rank":"2","remark":null,"own_sys":null,"is_root":"0","create_time":null,"creater":null,"update_time":null,"updater":null}],"database":"sys","es":1652168732000,"id":5,"isDdl":false,"mysqlType":{"stratum_id":"bigint(20)","stratum_name":"varchar(100)","deep":"int(2)","publish_portal":"varchar(32)","rank":"int(3)","remark":"varchar(500)","own_sys":"varchar(2)","is_root":"char(1)","create_time":"datetime","creater":"varchar(100)","update_time":"datetime","updater":"varchar(100)"},"old":[{"stratum_name":"监控中心","deep":"2"}],"pkNames":["stratum_id"],"sql":"","sqlType":{"stratum_id":-5,"stratum_name":12,"deep":4,"publish_portal":12,"rank":4,"remark":12,"own_sys":12,"is_root":1,"create_time":93,"creater":12,"update_time":93,"updater":12},"table":"auth_stratum","ts":1652168732228,"type":"UPDATE"}

# statement模式下的消息体

#insert消息体

{"data":null,"database":"sys","es":1652170744000,"id":2,"isDdl":false,"mysqlType":null,"old":null,"pkNames":null,"sql":"/* ApplicationName=DBeaver 21.2.3 - SQLEditor <Script-11.sql> */ INSERT INTO AUTH_STRATUM\r\n(stratum_id, stratum_name, deep, publish_portal, `rank`, remark, own_sys, is_root, create_time, creater, update_time, updater)\r\nVALUES(10004, '监控中心', 2, '8', 2, NULL, NULL, '0', NULL, NULL, NULL, NULL)","sqlType":null,"table":"AUTH_STRATUM","ts":1652170744592,"type":"INSERT"}

#delete消息体

{"data":null,"database":"sys","es":1652170284000,"id":1,"isDdl":false,"mysqlType":null,"old":null,"pkNames":null,"sql":"/* ApplicationName=DBeaver 21.2.3 - SQLEditor <Script-11.sql> */ delete from auth_stratum where stratum_id =10004","sqlType":null,"table":"auth_stratum","ts":1652170289848,"type":"DELETE"}

#update消息体

{"data":null,"database":"sys","es":1652170781000,"id":3,"isDdl":false,"mysqlType":null,"old":null,"pkNames":null,"sql":"/* ApplicationName=DBeaver 21.2.3 - SQLEditor <Script-11.sql> */ UPDATE sys.auth_stratum\n\tSET stratum_name='监控中心3',deep=1\n\tWHERE stratum_id=10004","sqlType":null,"table":"auth_stratum","ts":1652170781790,"type":"UPDATE"}

参考文档：Canal+Kafka实现MySQL与Redis数据同步 - 云+社区 - 腾讯云

使用Canal同步MySQL数据到Kafka 得到的数据中sql字段无值-问答-阿里云开发者社区-阿里云

qq_42174979

关注

0
点赞
踩
1

收藏

觉得还不错? 一键收藏
0
评论
canal+mysql+kafka[windows环境搭建]

针对公司资源环境申请都要走流程，麻烦死，故在本地搭建一套用于自测。1.zookeeper官网下载：Apache ZooKeeper这里用的是 apache-zookeeper-3.6.3-binzk配置修改:windows下启动记得把路径 apache-zookeeper-3.6.3-bin\conf里面的zoo_sample.cfg文件复制一份，改名为zoo.cfg 2.运行bin目录下的zkServer.cmd 【注：如...
复制链接

扫一扫