canal
canal copied to clipboard
alibaba
阿里巴巴 MySQL binlog 增量订阅&消费组件
我有一个需求，需要需要使用正则匹配数据库 我在instance 中配置的参数如下: canal.instance.filter.regex=test_db_.*\\.ts_dd 用来匹配以 test_db_ 开头的数据库中的 ts_dd 表，但是我发现好像实际仍然读取了所有表， 请问，有解决方案吗？ canal 版本 v1.1.5
canal 版本 为 1.1.7 数据库实例内有几千个表 ，配置 canal.mq.topic 参数值为 topic2 后 ，除了db1.table1表外的所有其它表的修改都会写消息进topic2 ，且只会写入0号分区 ，这部分消息实际上是不需要的，会引起0分区所在的kafka broker带宽瓶颈 ；本想配置 canal.instance.filter.black.regex 参数避免tps最大的 db2 库内的所有表的修改消息写入 topic2 中 ，但配置后不生效 ，同没有配置一样 ， topic1消息监听都正常 。具体配置如下 1> 请问没有配置监听的库与表的修改，有办法可以忽略掉不写进kafka吗 2> 如下...
- [ ] I have searched the [issues](https://github.com/alibaba/canal/issues) of this repository and believe that this is not a duplicate. - [ ] I have checked the [FAQ](https://github.com/alibaba/canal/wiki/FAQ) of this repository...
## Why you need it? We've identified that the default TLS version used in [AbstractRequest.java](https://github.com/alibaba/canal/blob/master/parse/src/main/java/com/alibaba/otter/canal/parse/inbound/mysql/rds/request/AbstractRequest.java#L198) is TLSv1, which is outdated and deprecated. ## How it could be? Given that TLSv1...
版本： image: canal/canal-server:v1.1.7 启动正常，成功作为mysql的slav，接受数据正常，但cpu一直飙高,找到该行代码是dbType没有值的nullpoint，不知道这个是连接的什么 canal.log 报错： 2023-11-14 03:53:13.595 [Druid-ConnectionPool-Create-119775511] ERROR com.alibaba.druid.pool.DruidDataSource - create connection RuntimeException java.lang.NullPointerException: null at com.alibaba.druid.pool.DruidAbstractDataSource.createPhysicalConnection(DruidAbstractDataSource.java:1746) at com.alibaba.druid.pool.DruidDataSource$CreateConnectionThread.run(DruidDataSource.java:2916) 2023-11-14 03:53:13.595 [Druid-ConnectionPool-Create-119775511] ERROR com.alibaba.druid.pool.DruidDataSource - create connection RuntimeException...
## Question The logs are too sparse to reflect the issue. It is unclear whether the connection to the message queue (MQ) has been successful, whether the binlog has been...
### environment * canal version 1.1.17 。 使用 canal.adapter-1.1.7 , MySQL to MySQL。 * mysql version 源 db 5.7.43-231000-log ， 目标 db 5.7.44。 ### Issue Description 2024-04-28 17:24:02.741 [pool-8-thread-1] INFO...
## Question ERROR com.rabbitmq.client.impl.ForgivingExceptionHandler - Consumer com.alibaba.otter.canal.connector.rabbitmq.consumer.CanalRabbitMQConsumer$1@3de73a3f (amq.ctag-dO4LXMfNCF9duzlo2FXtaA) method handleDelivery for channel AMQChannel(amqp://[email protected]:5672/,1) threw an exception for channel AMQChannel(amqp://[email protected]:5672/,1) com.rabbitmq.client.AlreadyClosedException: channel is already closed due to clean channel shutdown; protocol...
 DML: {"data":{"exception_status":null,"operate_type":"2","create_time":"2024-04-26 10:30:04","key_id":"1486411","remark":null,"version":null,"accept_data":null,"create_by":null,"update_time":"2024-04-26 10:30:04","is_return":"0","send_time":"2024-04-20 18:22:20","erp_accept_id":"45671045","accept_interface_type":null,"data_type":"mid_produce_task","site_id":"09106","fail_num":"0","handling_status":"2","update_by":null,"push_time":"2024-04-26 10:30:04"},"database":"tch","destination":"TCH","old":{"handling_status":"1"},"table":"erp_r_accept","type":"UPDATE"} 是配置原因吗？我看类似的问题在1.1.2出现过，我这个问题也是mysql2kafka出现的
