主从节点同步延迟变高，主从节点一直在重连 #256

pei-open · 2018-04-04T07:43:19Z

主节点日志：

W0404 07:41:24.268245 17899 pika_server.cc:1267] Could not purge 237, since it is already be used
I0404 07:41:27.192255 18080 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 07:41:27.238871 18080 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 07:41:30.239326 18080 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 07:41:30.285208 18080 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 07:41:33.285665 18080 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 07:41:33.328528 18080 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
W0404 07:41:34.268981 17899 pika_server.cc:1267] Could not purge 237, since it is already be used
I0404 07:41:36.328953 18080 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 07:41:36.372001 18080 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 07:41:39.372444 18080 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 07:41:39.430320 18080 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 07:41:42.430717 18080 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 07:41:42.477488 18080 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer

从节点日志：

E0404 07:39:36.285257 16632 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 14940
E0404 07:39:36.285454 16633 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 14677
E0404 07:39:36.285466 16629 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 15155
E0404 07:39:36.285475 16631 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 14953
E0404 07:39:36.285475 16628 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 15645
E0404 07:39:36.285480 16627 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 15662
E0404 07:39:36.285466 16630 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 15664
E0404 07:39:36.285467 16634 pika_binlog_bgworker.cc:112] command:set, start_time(s): 1522827576, duration(us): 15157

The text was updated successfully, but these errors were encountered:

Leviathan1995 · 2018-04-04T07:45:43Z

什么版本?

pei-open · 2018-04-04T07:46:43Z

2.3.3

Leviathan1995 · 2018-04-04T07:47:33Z

主从都是2.3.3吗现在主还在写入吗?

pei-open · 2018-04-04T07:49:25Z

从节点是2.3.1，主还在写

pei-open · 2018-04-04T07:49:35Z

我升级到2.3.3试试

pei-open · 2018-04-04T08:08:10Z

现在从节点的信息变成info了，但是好像还是在不断重连

I0404 08:05:54.580471 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8
I0404 08:05:57.628657 16879 pika_binlog_receiver_thread.cc:41] Master Binlog Sender: 10.11.2.108 connecting
I0404 08:05:57.628836 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8
I0404 08:06:00.675173 16879 pika_binlog_receiver_thread.cc:41] Master Binlog Sender: 10.11.2.108 connecting
I0404 08:06:00.675330 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8
I0404 08:06:03.720875 16879 pika_binlog_receiver_thread.cc:41] Master Binlog Sender: 10.11.2.108 connecting
I0404 08:06:03.721076 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8
I0404 08:06:06.765970 16879 pika_binlog_receiver_thread.cc:41] Master Binlog Sender: 10.11.2.108 connecting
I0404 08:06:06.766118 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8
I0404 08:06:09.815393 16879 pika_binlog_receiver_thread.cc:41] Master Binlog Sender: 10.11.2.108 connecting
I0404 08:06:09.815629 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8
I0404 08:06:12.861456 16879 pika_binlog_receiver_thread.cc:41] Master Binlog Sender: 10.11.2.108 connecting
I0404 08:06:12.861644 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8
I0404 08:06:15.907827 16879 pika_binlog_receiver_thread.cc:41] Master Binlog Sender: 10.11.2.108 connecting
I0404 08:06:15.908037 16879 pika_master_conn.cc:39] BinlogReceiverThread AccessHandle succeeded, My server id: 8 Master auth server id: 8

主节点还是下面这样

W0404 08:07:24.390429 17899 pika_server.cc:1267] Could not purge 248, since it is already be used
I0404 08:07:27.297178 18254 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 08:07:27.344449 18254 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 08:07:30.344875 18254 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 08:07:30.394187 18254 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 08:07:33.394608 18254 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 08:07:33.444864 18254 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
W0404 08:07:34.391208 17899 pika_server.cc:1267] Could not purge 248, since it is already be used
I0404 08:07:36.445292 18254 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 08:07:36.493350 18254 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 08:07:39.493803 18254 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK
W0404 08:07:39.543514 18254 pika_binlog_sender_thread.cc:313] BinlogSender send slave(10.11.2.109:10221) failed,  IO error: write error Connection reset by peer
I0404 08:07:42.543972 18254 pika_binlog_sender_thread.cc:258] BinlogSender Connect slave(10.11.2.109:10221) OK

能帮忙看一下，出现这个我是有什么东西配错了还是？

pei-open · 2018-04-04T08:12:38Z

我这边主节点的配置：

# Pika port
port : 9221
# Thread Number
thread-num : 1
# Sync Thread Number
sync-thread-num : 8
# Item count of sync thread queue
sync-buffer-size : 10
# Pika log path
log-path : ./log/
# Pika glog level: only INFO and ERROR
loglevel : INFO
# Pika db path
db-path : ./db/
# Pika write-buffer-size
write-buffer-size : 1073741824
# Pika timeout
timeout : 60
# Requirepass
requirepass :
# Masterauth
masterauth :
# Userpass
userpass :
# User Blacklist
userblacklist :
# Dump Prefix
dump-prefix :
# daemonize  [yes | no]
#daemonize : yes
daemonize : no
# slotmigrate  [yes | no]
#slotmigrate : no
slotmigrate : yes
# Dump Path
dump-path : ./dump/
# Expire-dump-days
dump-expire : 0
# pidfile Path
pidfile : ./pika.pid
# Max Connection
maxclients : 20000
# the per file size of sst to compact, defalut is 2M
target-file-size-base : 20971520
# Expire-logs-days
expire-logs-days : 7
# Expire-logs-nums
expire-logs-nums : 10
# Root-connection-num
root-connection-num : 10
# Slowlog-log-slower-than
slowlog-log-slower-than : 10000
# slave-read-only(yes/no, 1/0)
slave-read-only : false
# Pika db sync path
db-sync-path : ./dbsync/
# db sync speed(MB) max is set to 125MB, min is set to 0, and if below 0 or above 125, the value will be adjust to 125
db-sync-speed : 125
# The slave priority
slave-priority : 100
# network interface
#network-interface : eth1
# replication
#slaveof : master-ip:master-port

# CronTask, format: start-end/ratio, like 02-04/60, pika will check to schedule compaction between 2 to 4 o'clock everyday
#                   if the freesize/disksize > 60%. NOTICE:if compact-interval is set, compact-cron will be mask and disable.
#compact-cron :

# Compact-interval, format: interval/ratio, like 6/60, pika will check to schedule compaction every 6 hours,
#                           if the freesize/disksize > 60%. NOTICE:compact-interval is prior than compact-cron;
#compact-interval :

# server-id for hub
server-id : 1

# The peer-master config
double-master-ip :
double-master-port :
double-master-server-id :

###################
## Critical Settings
###################
# binlog file size: default is 100M,  limited in [1K, 2G]
binlog-file-size : 104857600
# Compression
compression : snappy
# max-background-flushes: default is 1, limited in [1, 4]
max-background-flushes : 1
# max-background-compactions: default is 2, limited in [1, 8]
max-background-compactions : 2
# max-cache-files default is 5000
max-cache-files : 5000
# max_bytes_for_level_multiplier: default is 10, you can change it to 5
max-bytes-for-level-multiplier : 10

从节点的配置

# Pika port
port : 9221
# Thread Number
thread-num : 1
# Sync Thread Number
sync-thread-num : 8
# Item count of sync thread queue
sync-buffer-size : 10
# Pika log path
log-path : ./log/
# Pika glog level: only INFO and ERROR
loglevel : INFO
# Pika db path
db-path : ./db/
# Pika write-buffer-size
write-buffer-size : 1073741824
# Pika timeout
timeout : 60
# Requirepass
requirepass :
# Masterauth
masterauth :
# Userpass
userpass :
# User Blacklist
userblacklist :
# Dump Prefix
dump-prefix :
# daemonize  [yes | no]
#daemonize : yes
daemonize : no
# slotmigrate  [yes | no]
#slotmigrate : no
slotmigrate : yes
# Dump Path
dump-path : ./dump/
# Expire-dump-days
dump-expire : 0
# pidfile Path
pidfile : ./pika.pid
# Max Connection
maxclients : 20000
# the per file size of sst to compact, defalut is 20M
target-file-size-base : 20971520
# Expire-logs-days
expire-logs-days : 7
# Expire-logs-nums
expire-logs-nums : 10
# Root-connection-num
root-connection-num : 10
# Slowlog-log-slower-than
slowlog-log-slower-than : 10000
# slave-read-only(yes/no, 1/0)
slave-read-only : true
# Pika db sync path
db-sync-path : ./dbsync/
# db sync speed(MB) max is set to 125MB, min is set to 0, and if below 0 or above 125, the value will be adjust to 125
db-sync-speed : 125
# The slave priority
slave-priority : 100
# network interface
#network-interface : eth1
# replication
#slaveof : master-ip:master-port
slaveof : *****

# CronTask, format: start-end/ratio, like 02-04/60, pika will check to schedule compaction between 2 to 4 o'clock everyday
#                   if the freesize/disksize > 60%. NOTICE:if compact-interval is set, compact-cron will be mask and disable.
#compact-cron :

# Compact-interval, format: interval/ratio, like 6/60, pika will check to schedule compaction every 6 hours,
#                           if the freesize/disksize > 60%. NOTICE:compact-interval is prior than compact-cron;
#compact-interval :

# server-id for hub
server-id : 1

# The peer-master config
double-master-ip :
double-master-port :
double-master-server-id :

###################
## Critical Settings
###################
# binlog file size: default is 100M,  limited in [1K, 2G]
binlog-file-size : 104857600
# Compression
compression : snappy
# max-background-flushes: default is 1, limited in [1, 4]
max-background-flushes : 1
# max-background-compactions: default is 2, limited in [1, 8]
max-background-compactions : 2
# max-cache-files default is 5000
max-cache-files : 5000
# max_bytes_for_level_multiplier: default is 10, you can change it to 5
max-bytes-for-level-multiplier : 10

Leviathan1995 · 2018-04-04T08:14:08Z

你目前能重启主的机器吗

pei-open · 2018-04-04T08:18:33Z

可以重启的。主的节点重启了服务，还是一样。重启机器也还是一样

Leviathan1995 · 2018-04-04T08:22:01Z

@oooldcoder QQ群: 294254078 沟通方便一点

renyankankan · 2019-07-02T04:05:11Z

主节点:
I0702 11:58:05.723393 1896 pika_binlog_sender_thread.cc:250] BinlogSender Connect slave(192.168.1.22:10221) OK
W0702 11:58:08.726336 1896 pika_binlog_sender_thread.cc:309] BinlogSender send slave(192.168.1.22:10221) failed, IO error: write error Broken pipe
从节点:
I0702 11:48:59.789088 10949 pika_binlog_receiver_thread.h:52] Master conn factory creat pika binlog conn ip_port192.168.1.20:49432
I0702 11:48:59.789964 10949 pika_binlog_receiver_conn.cc:156] BinlogReceiverThread AccessHandle failed, My server id: 2 Master auth server id: 1

请问怎么解决？

zerogtw · 2022-06-21T09:32:20Z

与 #256 (comment) 相同的现象

version: 3.0.16

表现同样是主从同步异常，但从 info Replication 看 lag 居然是 lag=0，即同步没有落后

不知道最终原因是怎样，有什么解决方案？

kernelai · 2022-06-21T09:52:50Z

升级版本吧。新版本是解决不少同步的问题的。

zerogtw · 2022-06-22T03:16:24Z

升级版本吧。新版本是解决不少同步的问题的。

我看新版本同步逻辑也改了很多，貌似只能升级大法了

AlexStocks · 2023-03-11T17:42:41Z

@kernelai 这个 issue 是不是可以关掉了？

* set_cache Co-authored-by: chejinge <chejinge@360.cn>

* add dependences * fix: add_ci (#229) add_ci Co-authored-by: wuxianrong <wuxianrong@360.cn> * formate code style && fix centos build bug * fix centos build bug * format code style * format * rename classname * format code * use cache define * upgrade rediscache version to v0.1.3 * change file name * using DEFER * fix github ci failure * add_string_cache【暂时不修改格式及代码风格，会在最后一个PR统一做修改】 (#237) add_string_cache * add_slave_cache (#243) Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix:cache string (#247) fix_cache_string * add_bitmap_cache (#255) * add_bitmap_cache Co-authored-by: chejinge <chejinge@360.cn> * add string cache cmd (#252) add_string_cache_cmd Co-authored-by: wuxianrong <wuxianrong@360.cn> * add list cache cmd (#250) add_list_cache_cmd Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache set command (#256) * set_cache Co-authored-by: chejinge <chejinge@360.cn> * add hash cache cmd (#251) add_hash_cache_cmd Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache zset command (#257) * cache zset command Co-authored-by: chejinge <chejinge@360.cn> * Update pika_zset.h * add Pika Cache Status (#259) Add Pika-Cache-Status Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache index * git revert * 【fix】cache Asynchronous transmission (#265) fix cache Asynchronous transmission Co-authored-by: wuxianrong <wuxianrong@360.cn> * add defer (#269) add_defer Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache index (#260) * cache index Co-authored-by: chejinge <chejinge@360.cn> Co-authored-by: wuxianrong <wuxianrong@360.cn> * Support for multiple databases (#275) * delete_pika_cache_manager * Support for multiple databases --------- Co-authored-by: wuxianrong <wuxianrong@360.cn> * smart pointer and lock granularity && set don't update cache (#277) Co-authored-by: chejinge <chejinge@360.cn> * fix_lock (#278) Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix_command_bug (#282) * fix_command_bug Co-authored-by: chejinge <chejinge@360.cn> * Fix del mget (#291) fix_del_command&&HMSET HMGET --------- Co-authored-by: chejinge <chejinge@360.cn> * bugfix:ttl&&exits command (#300) * fix_ttl_exits --------- Co-authored-by: chejinge <chejinge@360.cn> * fix: hash/list/set/zset test (#285) * fix hash/list test * fix set/zset test --------- Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix bitpos strlen msetnx * fix bitpos strlen msetnx * Update pika_kv.cc * Update pika_command.cc * fix: hash/zset test cache (#302) * fix hash/list test Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix Master-slave test * code format (#316) Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix:cache code style * fix:cache code style * fix * Supports multi-DB asynchronous data transfer (#317) * code format * support dbs --------- Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix conflict and change name * fix conflict and change name * fix conflict and change name * Update pika_admin.cc * Update pika_admin.cc * Initialization variable (#321) add_comment Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix_flushdb * fix: Cache flushdb (#322) fix_flushdb Co-authored-by: wuxianrong <wuxianrong@360.cn> * Fix cache mget (#323) * fix_mget * fix_lock_and_multi_caches * fix_mem_leak * fix_mem_leak * fix * add cacheclean command * fix coreedump * Fix:mem leak (#329) fix:hdel Co-authored-by: chejinge <chejinge@360.cn> * Update pika_admin.cc * Update pika.conf * Update pika.conf * fix_license * remove nullpter --------- Co-authored-by: chejinge <chejinge@360.cn> Co-authored-by: Mixficsol <838844609@qq.com> Co-authored-by: wuxianrong <wuxianrong@360.cn> Co-authored-by: Xin.Zh <dragoncharlie@foxmail.com> Co-authored-by: alexstocks <alexstocks@foxmail.com>

* add dependences * fix: add_ci (OpenAtomFoundation#229) add_ci Co-authored-by: wuxianrong <wuxianrong@360.cn> * formate code style && fix centos build bug * fix centos build bug * format code style * format * rename classname * format code * use cache define * upgrade rediscache version to v0.1.3 * change file name * using DEFER * fix github ci failure * add_string_cache【暂时不修改格式及代码风格，会在最后一个PR统一做修改】 (OpenAtomFoundation#237) add_string_cache * add_slave_cache (OpenAtomFoundation#243) Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix:cache string (OpenAtomFoundation#247) fix_cache_string * add_bitmap_cache (OpenAtomFoundation#255) * add_bitmap_cache Co-authored-by: chejinge <chejinge@360.cn> * add string cache cmd (OpenAtomFoundation#252) add_string_cache_cmd Co-authored-by: wuxianrong <wuxianrong@360.cn> * add list cache cmd (OpenAtomFoundation#250) add_list_cache_cmd Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache set command (OpenAtomFoundation#256) * set_cache Co-authored-by: chejinge <chejinge@360.cn> * add hash cache cmd (OpenAtomFoundation#251) add_hash_cache_cmd Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache zset command (OpenAtomFoundation#257) * cache zset command Co-authored-by: chejinge <chejinge@360.cn> * Update pika_zset.h * add Pika Cache Status (OpenAtomFoundation#259) Add Pika-Cache-Status Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache index * git revert * 【fix】cache Asynchronous transmission (OpenAtomFoundation#265) fix cache Asynchronous transmission Co-authored-by: wuxianrong <wuxianrong@360.cn> * add defer (OpenAtomFoundation#269) add_defer Co-authored-by: wuxianrong <wuxianrong@360.cn> * cache index (OpenAtomFoundation#260) * cache index Co-authored-by: chejinge <chejinge@360.cn> Co-authored-by: wuxianrong <wuxianrong@360.cn> * Support for multiple databases (OpenAtomFoundation#275) * delete_pika_cache_manager * Support for multiple databases --------- Co-authored-by: wuxianrong <wuxianrong@360.cn> * smart pointer and lock granularity && set don't update cache (OpenAtomFoundation#277) Co-authored-by: chejinge <chejinge@360.cn> * fix_lock (OpenAtomFoundation#278) Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix_command_bug (OpenAtomFoundation#282) * fix_command_bug Co-authored-by: chejinge <chejinge@360.cn> * Fix del mget (OpenAtomFoundation#291) fix_del_command&&HMSET HMGET --------- Co-authored-by: chejinge <chejinge@360.cn> * bugfix:ttl&&exits command (OpenAtomFoundation#300) * fix_ttl_exits --------- Co-authored-by: chejinge <chejinge@360.cn> * fix: hash/list/set/zset test (OpenAtomFoundation#285) * fix hash/list test * fix set/zset test --------- Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix bitpos strlen msetnx * fix bitpos strlen msetnx * Update pika_kv.cc * Update pika_command.cc * fix: hash/zset test cache (OpenAtomFoundation#302) * fix hash/list test Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix Master-slave test * code format (OpenAtomFoundation#316) Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix:cache code style * fix:cache code style * fix * Supports multi-DB asynchronous data transfer (OpenAtomFoundation#317) * code format * support dbs --------- Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix conflict and change name * fix conflict and change name * fix conflict and change name * Update pika_admin.cc * Update pika_admin.cc * Initialization variable (OpenAtomFoundation#321) add_comment Co-authored-by: wuxianrong <wuxianrong@360.cn> * fix_flushdb * fix: Cache flushdb (OpenAtomFoundation#322) fix_flushdb Co-authored-by: wuxianrong <wuxianrong@360.cn> * Fix cache mget (OpenAtomFoundation#323) * fix_mget * fix_lock_and_multi_caches * fix_mem_leak * fix_mem_leak * fix * add cacheclean command * fix coreedump * Fix:mem leak (OpenAtomFoundation#329) fix:hdel Co-authored-by: chejinge <chejinge@360.cn> * Update pika_admin.cc * Update pika.conf * Update pika.conf * fix_license * remove nullpter --------- Co-authored-by: chejinge <chejinge@360.cn> Co-authored-by: Mixficsol <838844609@qq.com> Co-authored-by: wuxianrong <wuxianrong@360.cn> Co-authored-by: Xin.Zh <dragoncharlie@foxmail.com> Co-authored-by: alexstocks <alexstocks@foxmail.com>

AlexStocks closed this as completed Apr 8, 2023

chejinge added a commit to chejinge/pika that referenced this issue Nov 7, 2023

cache set command (OpenAtomFoundation#256)

4fbb251

* set_cache Co-authored-by: chejinge <chejinge@360.cn>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

主从节点同步延迟变高，主从节点一直在重连 #256

主从节点同步延迟变高，主从节点一直在重连 #256

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

pei-open commented Apr 4, 2018

pei-open commented Apr 4, 2018

pei-open commented Apr 4, 2018

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

renyankankan commented Jul 2, 2019

zerogtw commented Jun 21, 2022

kernelai commented Jun 21, 2022

zerogtw commented Jun 22, 2022

AlexStocks commented Mar 11, 2023

主从节点同步延迟变高，主从节点一直在重连 #256

主从节点同步延迟变高，主从节点一直在重连 #256

Comments

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

pei-open commented Apr 4, 2018

pei-open commented Apr 4, 2018

pei-open commented Apr 4, 2018

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

pei-open commented Apr 4, 2018

Leviathan1995 commented Apr 4, 2018

renyankankan commented Jul 2, 2019

zerogtw commented Jun 21, 2022

kernelai commented Jun 21, 2022

zerogtw commented Jun 22, 2022

AlexStocks commented Mar 11, 2023