Canal dynamicTopic問題

Canal dynamicTopic問題

未來同事跑了幾個月的canal突然報下面的錯, 使用了dynamicTopic. 其實我沒有用過dynamicTopic, 只能搜一搜issue

關於dynamicTopic和partitionHash的說明

canal.mq.dynamicTopic 表達式說明

canal 1.1.3版本之後, 支持配置格式：schema 或 schema.table，多個配置之間使用逗號或分號分隔

例子1：test\\.test 指定匹配的單表，發送到以test_test爲名字的topic上
例子2：.*\\..* 匹配所有表，則每個表都會發送到各自表名的topic上
例子3：test 指定匹配對應的庫，一個庫的所有表都會發送到庫名的topic上
例子4：test\\.* 指定匹配的表達式，針對匹配的表會發送到各自表名的topic上
例子5：test,test1\\.test1，指定多個表達式，會將test庫的表都發送到test的topic上，test1\\.test1的表發送到對應的test1_test1 topic上，其餘的表發送到默認的canal.mq.topic值
爲滿足更大的靈活性，允許對匹配條件的規則指定發送的topic名字，配置格式：topicName:schema 或 topicName:schema.table

例子1: test:test\\.test 指定匹配的單表，發送到以test爲名字的topic上
例子2: test:.*\\..* 匹配所有表，因爲有指定topic，則每個表都會發送到test的topic下
例子3: test:test 指定匹配對應的庫，一個庫的所有表都會發送到test的topic下
例子4：testA:test\\.* 指定匹配的表達式，針對匹配的表會發送到testA的topic下
例子5：test0:test,test1:test1\\.test1，指定多個表達式，會將test庫的表都發送到test0的topic下，test1\\.test1的表發送到對應的test1的topic下，其餘的表發送到默認的canal.mq.topic值

大家可以結合自己的業務需求，設置匹配規則，建議MQ開啓自動創建topic的能力

canal.mq.partitionHash 表達式說明

canal 1.1.3版本之後, 支持配置格式：schema.table:pk1^pk2，多個配置之間使用逗號分隔

例子1：test\\.test:pk1^pk2 指定匹配的單表，對應的hash字段爲pk1 + pk2
例子2：.*\\..*:id 正則匹配，指定所有正則匹配的表對應的hash字段爲id
例子3：.*\\..*:$pk$ 正則匹配，指定所有正則匹配的表對應的hash字段爲表主鍵(自動查找)
例子4: 匹配規則啥都不寫，則默認發到0這個partition上
例子5：.*\\..* ，不指定pk信息的正則匹配，將所有正則匹配的表,對應的hash字段爲表名
按表hash: 一張表的所有數據可以發到同一個分區，不同表之間會做散列 (會有熱點表分區過大問題)
例子6: test\\.test:id,.\\..* , 針對test的表按照id散列,其餘的表按照table散列

注意：大家可以結合自己的業務需求，設置匹配規則，多條匹配規則之間是按照順序進行匹配(命中一條規則就返回)

其他詳細參數可參考Canal AdminGuide

canal.log報INVALID_TOPIC_EXCEPTION

2020-01-10 15:58:31.552 [canal-instance-scan-0] INFO  com.alibaba.otter.canal.deployer.CanalController - auto notify start example successful.
2020-01-10 16:37:26.946 [canal-instance-scan-0] INFO  com.alibaba.otter.canal.deployer.CanalController - auto notify start mgr_fanboshi successful.
2020-01-10 16:38:03.992 [kafka-producer-network-thread | producer-1] WARN  org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Error while fetching metadata with correlation id 10 : {=INVALID_TOPIC_EXCEPTION}
2020-01-10 16:38:04.096 [kafka-producer-network-thread | producer-1] WARN  org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Error while fetching metadata with correlation id 11 : {=INVALID_TOPIC_EXCEPTION}
2020-01-10 16:38:04.200 [kafka-producer-network-thread | producer-1] WARN  org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Error while fetching metadata with correlation id 12 : {=INVALID_TOPIC_EXCEPTION}
2020-01-10 16:38:04.304 [kafka-producer-network-thread | producer-1] WARN  org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Error while fetching metadata with correlation id 13 : {=INVALID_TOPIC_EXCEPTION}
2020-01-10 16:38:04.409 [kafka-producer-network-thread | producer-1] WARN  org.apache.kafka.clients.NetworkClient - [Producer clientId=producer-1] Error while fetching metadata with correlation id 14 : {=INVALID_TOPIC_EXCEPTION}

instance的log中會報錯

2020-01-10 16:37:27.159 [destination = mgr_fanboshi , address = /172.18.8.200:3399 , EventParser] WARN  c.a.o.c.p.inbound.mysql.rds.RdsBinlogEventParserProxy - ---> find start position successfully, EntryPosition[included=false,journalName=0080323399-mysql-bin.000004,position=1065960584,serverId=<null>,gtid=69ce1dcb-1b67-5e4b-9945-7cc64c64a14f:1-566281:1000009-2590159:3005066-3017688,
ce947b65-6b70-539b-8e6a-59e9bcde28a0:206083443-206083524:207812793-207825891:207921053-207921085,
d58aa5c2-b773-5944-bfe9-0a1142ef87f4:1706527:2447252-2447264,
f5d4a39c-7800-52ec-b181-8c751ba2d078:868915-869106:1968590-1968591,timestamp=<null>] cost : 2ms , the next step is binlog dump
2020-01-10 16:39:03.987 [pool-3-thread-2] ERROR com.alibaba.otter.canal.kafka.CanalKafkaProducer - java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.
java.lang.RuntimeException: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.
        at com.alibaba.otter.canal.kafka.CanalKafkaProducer.produce(CanalKafkaProducer.java:215) ~[canal.server-1.1.4.jar:na]
        at com.alibaba.otter.canal.kafka.CanalKafkaProducer.send(CanalKafkaProducer.java:179) ~[canal.server-1.1.4.jar:na]
        at com.alibaba.otter.canal.kafka.CanalKafkaProducer.send(CanalKafkaProducer.java:117) ~[canal.server-1.1.4.jar:na]
        at com.alibaba.otter.canal.server.CanalMQStarter.worker(CanalMQStarter.java:183) [canal.server-1.1.4.jar:na]
        at com.alibaba.otter.canal.server.CanalMQStarter.access$500(CanalMQStarter.java:23) [canal.server-1.1.4.jar:na]
        at com.alibaba.otter.canal.server.CanalMQStarter$CanalMQRunnable.run(CanalMQStarter.java:225) [canal.server-1.1.4.jar:na]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.
        at org.apache.kafka.clients.producer.KafkaProducer$FutureFailure.<init>(KafkaProducer.java:1150) ~[kafka-clients-1.1.1.jar:na]
        at org.apache.kafka.clients.producer.KafkaProducer.doSend(KafkaProducer.java:846) ~[kafka-clients-1.1.1.jar:na]
        at org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:784) ~[kafka-clients-1.1.1.jar:na]
        at org.apache.kafka.clients.producer.KafkaProducer.send(KafkaProducer.java:671) ~[kafka-clients-1.1.1.jar:na]
        at com.alibaba.otter.canal.kafka.CanalKafkaProducer.produce(CanalKafkaProducer.java:199) ~[canal.server-1.1.4.jar:na]
        ... 8 common frames omitted
Caused by: org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.

搜到一個issue給了我一些啓發https://github.com/alibaba/canal/issues/1716

在instance.properties裏面配置
同步庫配置
canal.instance.filter.regex=A\\..*,B\\..*,C\\..*

消息隊列配置
使用正則路由schema和table
格式topic:schema.table,topic:schema.table,topic:schema.table
canal.mq.dynamicTopic=topic_A:A,topic_B:B,topic_C:C
最好配置一個canal.mq.topic作爲默認的topic，在實踐中發現，有一些mysql schema的binlog也會讀進來（建表語句，grant語句等），如果沒有這個默認的topic，會報找不到分區的錯誤，從而導致canal停止寫入。
canal.mq.topic=a_default_topic

分區設置

1. 如果每個topic只有一個分區設置如下
   canal.mq.partition=0
2. 如果每個topic有多個分區，且希望按照表名做hash進行如下配置
   # hash partition config
canal.mq.partitionsNum=3
canal.mq.partitionHash=.*\\..*

是不是canal.mq.topic這個參數隨便寫一個存在的topic，然後主要設置在這裏對吧？canal.mq.dynamicTopic=topic_A:A,topic_B:B,topic_C:C

是的。canal.mq.topic算是一個默認的，沒有匹配到的schema和table的日誌都會輸入到那個默認的裏面去。消費的時候只關心你設置的動態分區。

我的理解就是一些不是我們匹配規則所需要的消息因爲沒有配置默認topic而找不到topic可寫, 於是纔會報錯INVALID_TOPIC_EXCEPTION

雖然未來同事配置了canal.instance.filter.regex=broker\\..* 但是有可能grant之類的語句還是會有問題吧

最後附上自己1.1.4的配置吧

canal.properties

#################################################
#########               common argument         #############
#################################################
# tcp bind ip
canal.ip = 172.18.8.32
# register ip to zookeeper
canal.register.ip = 172.18.8.32
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.18.12.212:2181,172.18.12.213:2181
# flush data to zk
canal.zookeeper.flush.period = 1000
canal.withoutNetty = true
# 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 = false
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 =
# 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 = 172.18.12.212:9092
canal.mq.retries = 0
canal.mq.batchSize = 16384
canal.mq.maxRequestSize = 33554432
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.transaction = false
canal.mq.extraParams.enable.idempotence=true
canal.mq.extraParams.max.in.flight.requests.per.connection=1
#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"

instance.properties

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

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

# position info
canal.instance.master.address=172.18.8.200:3372
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=false
#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_r
canal.instance.dbPassword=canal1234!@#$
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=fanboshi\\..*
# 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=
#canal.mq.topic=cherry_default
# dynamic topic route by schema or table regex
#canal.mq.dynamicTopic=mytest1.user,mytest2\\..*,.*\\..*
canal.mq.dynamicTopic= cherry:fanboshi
#canal.mq.partition=0
# hash partition config
#canal.mq.partitionsNum=3
#canal.mq.partitionHash=test.table:id^name,.*\\..*
#################################################