使用Canal监听数据库配置时所报的异常记录
60 浏览量
2021-01-20
12:19:50
上传
评论
收藏 280KB PDF 举报
使用使用Canal监听数据库配置时所报的异常记录监听数据库配置时所报的异常记录
使用使用docker容器来安装容器来安装canal和和mysql
待解决的问题：监听待解决的问题：监听mysql以后对数据据库所做的操作以后对数据据库所做的操作canal监听不到监听不到
怀疑怀疑canal没有配置好，检查没有配置好，检查canal的日志后发现异常：的日志后发现异常：
2020-02-15 10:58:24.506 [destination = example , address = /192.168.0.105:3306 , EventParser] ERROR com.alibaba.otter.canal.common.alarm.LogAlarmHandler –
destination:example[com.alibaba.otter.canal.parse.exception.CanalParseException: command : ‘show master status’ has an error! pls check. you need (at least one of) the SUPER,REPLICATION
CLIENT privilege(s) for this operation
]
在这之前已经配置好了在这之前已经配置好了mysql和和canal的两个配置文件：的两个配置文件：
这个问题解决不了，就在网上查看了好多篇文档，都说时这个问题解决不了，就在网上查看了好多篇文档，都说时canal中用户名和密码在中用户名和密码在MySQL中没有配置好，创建的用户名和密码都是中没有配置好，创建的用户名和密码都是canal
*************************** 5. row ***************************
host: %
user: canal
select_priv: Y
insert_priv: Y
update_priv: Y
delete_priv: Y
5 rows in set (0.00 sec)
还把还把MySQL的配置文件也给改了一下，打开了的配置文件也给改了一下，打开了mysql的日志的日志
[mysqld] skip-grant-tables
[mysqld] log-bin=mysql-bin #开启日志监控
binlog-format=ROW #监控模式为ROW
server_id=1 #配置mysql replaction需要定义，不能和canal的slaveId重复
切记：配置完成后重启切记：配置完成后重启mysql——>docker restart mysql
查看查看canal的配置：的配置：
canal.properties
[root@f3ff70f9ae8d canal-server]# vi conf/canal.properties
#################################################
######### common argument #############
#################################################
#canal.manager.jdbc.url=jdbc:mysql://127.0.0.1:3306/canal_manager?useUnicode=true&characterEncoding=UTF-8
#canal.manager.jdbc.username=root
#canal.manager.jdbc.password=121212
canal.id = 1001
canal.ip =
canal.port = 11111
canal.metrics.pull.port = 11112
canal.zkServers =
# 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
资源评论
