pika icon indicating copy to clipboard operation
pika copied to clipboard

主库一直打warning日志,主从不同步

Open luger1990 opened this issue 4 years ago • 4 comments

主库一直打印Could not purge 179, since it is already be used warning日志,然后从库没有同步主库的数据,从库的info如下:

# Replication(SLAVE)
role:slave
master_host:10.0.208.2
master_port:9042
master_link_status:up
slave_priority:100
slave_read_only:1
db0 binlog_offset=179 30537223,safety_purge=write2file169
db1 binlog_offset=0 0,safety_purge=none
db2 binlog_offset=0 0,safety_purge=none
db3 binlog_offset=0 0,safety_purge=none
db4 binlog_offset=0 0,safety_purge=none
db5 binlog_offset=0 0,safety_purge=none

请问这是什么问题?

luger1990 avatar Jan 04 '22 06:01 luger1990

pika的版本号是多少?出现这条日志的原因是master的定期删除binlog的流程发现,这条binlog还没有被slave同步。因此不会删除。请查看slave 同步是否异常。

kernelai avatar Jan 04 '22 06:01 kernelai

pika的版本号是多少?出现这条日志的原因是master的定期删除binlog的流程发现,这条binlog还没有被slave同步。因此不会删除。请查看slave 同步是否异常。

pika版本为:Pika module 3.3.6 slave节点倒没有什么错误日志,日志如下:

W1216 00:11:18.703060  5727 pika_stable_log.cc:71] purge process already exist
W1216 00:11:35.380177  5731 pika_repl_bgworker.cc:170] Check SessionId Mismatch: 10.0.208.2:9042, (db0:0) expected_session: 0, actual_session:1
W1216 00:11:35.380362  5727 pika_stable_log.cc:71] purge process already exist
W1216 00:11:35.384837  5731 pika_repl_bgworker.cc:175] Check Session failed db0_0
W1216 00:11:35.384876  5727 pika_stable_log.cc:71] purge process already exist
W1216 00:11:35.384896  5727 pika_stable_log.cc:71] purge process already exist
W1216 00:11:35.384902  5727 pika_stable_log.cc:71] purge process already exist
W1216 00:11:35.384909  5727 pika_stable_log.cc:71] purge process already exist

luger1990 avatar Jan 04 '22 07:01 luger1990

W1216 00:11:35.380177 5731 pika_repl_bgworker.cc:170] Check SessionId Mismatch: 10.0.208.2:9042, (db0:0) expected_session: 0, actual_session:1 从上连接异常,这个一般是由网络割接导致。观察下主从lag是多少?是一直增大吗?

kernelai avatar Jan 04 '22 07:01 kernelai

W1216 00:11:35.380177 5731 pika_repl_bgworker.cc:170] Check SessionId Mismatch: 10.0.208.2:9042, (db0:0) expected_session: 0, actual_session:1 从上连接异常,这个一般是由网络割接导致。观察下主从lag是多少?是一直增大吗?

目前重启了一下从库就好了,出问题的时候lag一直没变

luger1990 avatar Jan 04 '22 08:01 luger1990