一、目标:异库单库多表
实现不同数据库实例下,同名数据库下多张表的实时同步。
canal实验版本:v1.1.4
1.1 canal组件资源分配
序号 | canal组件 | host | ip | 服务方式(serverMode) | usage |
---|---|---|---|---|---|
1 | canal.deployer | cdh03 | 11111 | tcp(push) | 触发binlog生成 |
2 | canal.adapter | cdh05 | 8091(默认8081可能与flink的冲突) | tcp(pull) | 接收binlog,过滤出匹配的库表binlog并在落地库中replay |
1.2 canal.adaptor中源、目标配置说明
序号 | DB IP | DB端口 | db.tbl_name | 作用 |
---|---|---|---|---|
1 | 111.111.111.111 | 3306 | rtdw_test_gmall.holiday_info | 源库表,通过正则表达式订阅全库表binlog |
2 | 222.222.222.222 | 3306 | rtdw_test_gmall2.holiday_info | 目标库表,通过tcp方式根据source订阅规则,读取数据落地至destination中 |
二、canal server端
2.1 主配置文件
cd /data/canal.deployer-for-rdb-1.1.4/conf
canal.properties
#################################################
######### common argument #############
#################################################
# tcp bind ip
canal.ip = cdh03_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 = cdh03:2181,cdh04:2181,cdh05:2181
# flush data to zk
canal.zookeeper.flush.period = 1000
canal.withoutNetty = false
# tcp, kafka, RocketMQ
canal.serverMode = tcp
# 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 # canal.adaptor在后续订阅此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 = cdh03:9092,cdh04:9092,cdh05: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.1 子配置文件
cd /data/canal.deployer-for-rdb-1.1.4/conf/example
instance.properties
1 #################################################
2 ## mysql serverId , v1.0.26+ will autoGen
3 canal.instance.mysql.slaveId=1234
4
5 # enable gtid use true/false
6 canal.instance.gtidon=false
7
8 # position info
9 canal.instance.master.address=111.111.111.111:3306 #待监听的源数据库ip+port
10 canal.instance.master.journal.name=
11 canal.instance.master.position=
12 canal.instance.master.timestamp=
13 canal.instance.master.gtid=
14
15 # rds oss binlog
16 canal.instance.rds.accesskey=
17 canal.instance.rds.secretkey=
18 canal.instance.rds.instanceId=
19
20 # table meta tsdb info
21 canal.instance.tsdb.enable=true
22 #canal.instance.tsdb.url=jdbc:mysql://127.0.0.1:3306/canal_tsdb
23 #canal.instance.tsdb.dbUsername=canal
24 #canal.instance.tsdb.dbPassword=canal
25
26 #canal.instance.standby.address =
27 #canal.instance.standby.journal.name =
28 #canal.instance.standby.position =
29 #canal.instance.standby.timestamp =
30 #canal.instance.standby.gtid=
31
32 # username/password
33 canal.instance.dbUsername=canal
34 canal.instance.dbPassword=canal
35 canal.instance.connectionCharset = UTF-8
36 # enable druid Decrypt database password
37 canal.instance.enableDruid=false
38 #canal.instance.pwdPublicKey=MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALK4BUxdDltRRE5/zXpVEVPUgunvscYFtEip3pmLlhrWpacX7y7GCMo2/JM6LeHmiiNdH1FWgGCpUfircSwlWKUCAwEAAQ==
39
40 # table regex
41 #canal.instance.filter.regex=.*\\..*
42 canal.instance.filter.regex=rtdw_test_gmall\\..*
43 # table black regex
44 canal.instance.filter.black.regex=
45 # table field filter(format: schema1.tableName1:field1/field2,schema2.tableName2:field1/field2)
46 #canal.instance.filter.field=test1.t_product:id/subject/keywords,test2.t_company:id/name/contact/ch
47 # table field black filter(format: schema1.tableName1:field1/field2,schema2.tableName2:field1/field2)
48 #canal.instance.filter.black.field=test1.t_product:subject/product_image,test2.t_company:id/name/contact/ch
49
50 # mq config
51 canal.mq.topic=binlog_rtdw_test_gmall
52 # dynamic topic route by schema or table regex
53 #canal.mq.dynamicTopic=mytest1.user,mytest2\\..*,.*\\..*
54 canal.mq.partition=0
55 # hash partition config
56 #canal.mq.partitionsNum=3
57 #canal.mq.partitionHash=test.table:id^name,.*\\..*
58 #################################################
三、canal adaptor端
3.1 主配置文件
cd /data/canal.adapter-1.1.4/conf
application.yml
1 server:
2 port: 8091
3 spring:
4 jackson:
5 date-format: yyyy-MM-dd HH:mm:ss
6 time-zone: GMT+8
7 default-property-inclusion: non_null
8
9 canal.conf:
10 mode: tcp # tcp方式监听DBMS binlog变化,其他可选项:kafka rocketMQ
11 canalServerHost: cdh03_ip:11111
12 # zookeeperHosts: slave1:2181
13 # mqServers: 127.0.0.1:9092 #or rocketmq
14 # flatMessage: true
15 batchSize: 500
16 syncBatchSize: 1000
17 retries: 0
18 timeout:
19 accessKey:
20 secretKey:
21 srcDataSources: # Mysql source address
22 myDS1:
23 url: jdbc:mysql://111.111.111.111:3306/rtdw_test_gmall?useUnicode=true # 源库
24 username: root
25 password: password
26 canalAdapters: # 列表格式
27 - instance: example # canal instance Name or mq topic name:【实例名,需与canal.deployer中配置项“canal.destinations”的value保持严格一致】
28 groups:
29 - groupId: g1 #组ID
30 outerAdapters:
31 - name: logger
32 - name: rdb
33 key: mysql1 #后续根据此key进行溯源
34 properties:
35 jdbc.driverClassName: com.mysql.jdbc.Driver
36 jdbc.url: jdbc:mysql://222.222.222.222:3306/rtdw_test_gmall2?useUnicode=true
37 jdbc.username: root
38 jdbc.password: password
注意:
1、这里 canalAdapters 是个列表,下可以配置多个instance
2、多个instance配置成一模一样,canal.adapter组件也不会报错,但没有意义。有多个数据源,请配置不同不同的instance、groupId、key,以区分不同的映射。
3、srcDataSources为源库信息,canalAdapters.instance 为目标库的配置。
3.2 子配置文件
adapter模块是通过热加载rdb⽬录下的yml配置⽂件来做到同步数据到指定数据库的目的,所以这块需要引用此前主配置文件中定义的canal服务端信息 和 数据源信息。
cd /data/canal.adapter-1.1.4/conf/rdb/
test1.yml
1 dataSourceKey: myDS1
2 destination: example
3 groupId: g1
4 outerAdapterKey: mysql1
5 concurrent: true
6 dbMapping:
7 database: rtdw_test_gmall
8 table: holiday_info
9 targetTable: rtdw_test_gmall2.holiday_info
10 targetPk:
11 holiday_id: holiday_id
12 mapAll: true
test2.yml
1 dataSourceKey: myDS1
2 destination: example
3 groupId: g1
4 outerAdapterKey: mysql1
5 concurrent: true
6 dbMapping:
7 database: rtdw_test_gmall
8 table: base_region
9 targetTable: rtdw_test_gmall2.base_region
10 targetPk:
11 id: id
12 mapAll: true
四、注意事项
1、>>>>>>>>>>>>>> example2在canal deployer中没有配置:
2022-06-14 18:27:15.625 [Thread-6] INFO c.a.o.canal.adapter.launcher.loader.CanalAdapterWorker - =============> Disconnect destination: example2 <=============
2022-06-14 18:27:16.625 [Thread-6] INFO c.a.o.canal.adapter.launcher.loader.CanalAdapterWorker - =============> Start to connect destination: example2 <=============
2022-06-14 18:27:16.626 [Thread-6] INFO c.a.o.canal.adapter.launcher.loader.CanalAdapterWorker - =============> Start to subscribe destination: example2 <=============
2022-06-14 18:27:16.666 [Thread-6] ERROR c.a.o.canal.adapter.launcher.loader.CanalAdapterWorker - process error!
com.alibaba.otter.canal.protocol.exception.CanalClientException: failed to subscribe with reason: something goes wrong with channel:[id: 0x17883441, /cdh05:56704 => /cdh03:11111], exception=com.alibaba.otter.canal.server.exception.CanalServerException: destination:example2 should start first
at com.alibaba.otter.canal.client.impl.SimpleCanalConnector.subscribe(SimpleCanalConnector.java:249)
at com.alibaba.otter.canal.client.impl.SimpleCanalConnector.subscribe(SimpleCanalConnector.java:226)
at com.alibaba.otter.canal.adapter.launcher.loader.CanalAdapterWorker.process(CanalAdapterWorker.java:90)
at java.lang.Thread.run(Thread.java:745)
2、>>>>>>>>>>>>>>> instance/groupId/key not match
2022-06-14 18:48:20.132 [pool-8-thread-1] ERROR c.a.o.canal.adapter.launcher.loader.CanalAdapterWorker - java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.RuntimeException: java.sql.SQLException: connection holder is null
java.lang.RuntimeException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.RuntimeException: java.sql.SQLException: connection holder is null
at com.alibaba.otter.canal.client.adapter.rdb.RdbAdapter.sync(RdbAdapter.java:171)
at com.alibaba.otter.canal.adapter.launcher.loader.AbstractCanalAdapterWorker.batchSync(AbstractCanalAdapterWorker.java:201)
at com.alibaba.otter.canal.adapter.launcher.loader.AbstractCanalAdapterWorker.lambda$null$1(AbstractCanalAdapterWorker.java:62)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at com.alibaba.otter.canal.adapter.launcher.loader.AbstractCanalAdapterWorker.lambda$null$2(AbstractCanalAdapterWorker.java:58)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.alibaba.otter.canal.protocol.exception.CanalClientException: something goes wrong with reason: something goes wrong with channel:[id: 0x60e55f17, /cdh05:60624 => /cdh03:11111], exception=com.alibaba.otter.canal.server.exception.CanalServerException: ack error , clientId:1001 batchId:224 is not exist , please check
at com.alibaba.otter.canal.client.CanalMessageDeserializer.deserializer(CanalMessageDeserializer.java:46)
... 5 common frames omitted
可以获取到binlog日志,但无法解析。
3、>>>>>>>>>>>>>>>修改rdb中子配置文件,可以看到log中是热部署了,但经过测试是并未加载到最新的配置,需要手工重启canal.adaptor进程
2022-06-15 11:27:55.802 [Thread-3] INFO c.a.o.canal.client.adapter.rdb.monitor.RdbConfigMonitor - Change a rdb mapping config: test3_1dbAllTables.yml of canal adapter
2022-06-15 11:27:55.803 [Thread-5] INFO c.a.o.canal.client.adapter.rdb.monitor.RdbConfigMonitor - Change a rdb mapping config: test3_1dbAllTables.yml of canal adapter
2022-06-15 11:28:13.804 [Thread-3] INFO c.a.o.canal.client.adapter.rdb.monitor.RdbConfigMonitor - Delete a rdb mapping config: mytest_user.yml of canal adapter
4、>>>>>>>>>>>>>>>配置不存在的groupId,在启动adaptor时在rdb配置文件中找不到,将引发错误
5、rdb中如果将test1.yml与test2.yml中的内容合并到一个yml配置文件中,则只有最后一个配置会生效;如果配置到多个文件中,则都会生效。