Describe the bug
I trying failover to other node and its failover but not on selected node
*Infra
Six redis node kc-redis01 192.168.51.160 kc-redis02 192.168.51.161 kc-redis03:192.168.51.162 kc-redis04 192.168.51.171 kc-redis05 192.168.51.172 kc-redis06 192.168.51.173
& sentinel node.
Expected behavi# Describe the bug**
I trying failover to other node and its failover but not on selected node
To reproduce
Six redis node kc-redis01 192.168.51.160 kc-redis02 192.168.51.161 kc-redis03:192.168.51.162 kc-redis04 192.168.51.171 kc-redis05 192.168.51.172 kc-redis06 192.168.51.173
& sentinel node.
**Expected behavi# redis-cli -p 6378 -h kc-redis02 -a test INFO replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Replication
role:slave master_host:192.168.51.160 master_port:6378 master_link_status:down master_last_io_seconds_ago:-1 master_sync_in_progress:0 slave_read_repl_offset:88443 slave_repl_offset:88443 master_link_down_since_seconds:65 slave_priority:10 slave_read_only:1 replica_announced:1 connected_slaves:0 master_failover_state:no-failover master_replid:711eb0dbf68b78e5516212354048e1201e01b481 master_replid2:0000000000000000000000000000000000000000 master_repl_offset:88443 second_repl_offset:-1 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:88443
redis-cli -p 6378 -h kc-redis03] -a test INFO replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Replication
role:master connected_slaves:1 slave0:ip=192.168.51.172,port=6378,state=online,offset=0,lag=1 master_failover_state:no-failover master_replid:e76e4934db7e7aefdcc355b9f02e881fcbca9b6c master_replid2:711eb0dbf68b78e5516212354048e1201e01b481 master_repl_offset:88770 second_repl_offset:88444 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:88770
redis-cli p 26378 -h kc-sen01 INFO sentinel
Sentinel
sentinel_masters:1 sentinel_tilt:0 sentinel_running_scripts:0 sentinel_scripts_queue_length:0 sentinel_simulate_failure_flags:0 master0:name=redis-master-dc1,status=ok,address=192.168.51.162:6378,slaves=5,sentinels=3
Switch:
redis-cli --p 6378 -h kc-redis03 -a test FAILOVER TO 192.168.51.171 6378
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. OK
After:
redis-cli -p 6378 -h kc-redis03 -a test INFO replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Replication
role:slave master_host:192.168.51.171 master_port:6378 master_link_status:up master_last_io_seconds_ago:2 master_sync_in_progress:0 slave_read_repl_offset:135433 slave_repl_offset:135433 slave_priority:10 slave_read_only:1 replica_announced:1 connected_slaves:3 slave0:ip=192.168.51.161,port=6378,state=online,offset=135433,lag=1 slave1:ip=192.168.51.173,port=6378,state=online,offset=135433,lag=1 slave2:ip=192.168.51.172,port=6378,state=online,offset=135433,lag=1 master_failover_state:no-failover master_replid:5c529e48e39438475b2d5a7868893010377097d8 master_replid2:e76e4934db7e7aefdcc355b9f02e881fcbca9b6c master_repl_offset:135433 second_repl_offset:131279 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:135433
redis-cli - -p 6378 -h kc-redis04 -a test INFO replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Replication
role:master connected_slaves:1 slave0:ip=192.168.51.162,port=6378,state=online,offset=136359,lag=0 master_failover_state:no-failover master_replid:5c529e48e39438475b2d5a7868893010377097d8 master_replid2:e76e4934db7e7aefdcc355b9f02e881fcbca9b6c master_repl_offset:136359 second_repl_offset:131279 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:136359
But finally failovers goes to node 02:
redis-cli -p 6378 -h kc-redis04 -a test INFO replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Replication
role:master connected_slaves:1 slave0:ip=192.168.51.162,port=6378,state=online,offset=144761,lag=1 master_failover_state:no-failover master_replid:5c529e48e39438475b2d5a7868893010377097d8 master_replid2:e76e4934db7e7aefdcc355b9f02e881fcbca9b6c master_repl_offset:145065 second_repl_offset:131279 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:145065
redis-cli -p 6378 -h kc-redis04 -a test INFO replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Replication
role:slave master_host:192.168.51.161 master_port:6378 master_link_status:up master_last_io_seconds_ago:0 master_sync_in_progress:0 slave_read_repl_offset:147543 slave_repl_offset:147543 slave_priority:20 slave_read_only:1 replica_announced:1 connected_slaves:0 master_failover_state:no-failover master_replid:c8f1716253437bef41c2ade8b5c6811258ea24c1 master_replid2:0000000000000000000000000000000000000000 master_repl_offset:147543 second_repl_offset:-1 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:147369 repl_backlog_histlen:175
redis-cli -p 26378 -h kc-sen01 INFO sentinel
Sentinel
sentinel_masters:1 sentinel_tilt:0 sentinel_running_scripts:0 sentinel_scripts_queue_length:0 sentinel_simulate_failure_flags:0 master0:name=redis-master-dc1,status=ok,address=192.168.51.161:6378,slaves=5,sentinels=3
redis-cli -p 6378 -h kc-redis04 -a test INFO replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
Replication
role:slave master_host:192.168.51.161 master_port:6378 master_link_status:up master_last_io_seconds_ago:0 master_sync_in_progress:0 slave_read_repl_offset:152283 slave_repl_offset:152283 slave_priority:20 slave_read_only:1 replica_announced:1 connected_slaves:1 slave0:ip=192.168.51.162,port=6378,state=online,offset=152131,lag=1 master_failover_state:no-failover master_replid:c8f1716253437bef41c2ade8b5c6811258ea24c1 master_replid2:0000000000000000000000000000000000000000 master_repl_offset:152283 second_repl_offset:-1 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:147369 repl_backlog_histlen:4915
Expect Switch to selected replica
A description of what you expected to happen.
Additional information
Any additional information that is relevant to the problem.
Comment From: sundb
can you give the logs from kc-redis03 and 192.168.51.171 after FAILOVER.
Comment From: kamilcieslak5100
Hi, thanks for response.
Log from redis04
.-__ ''-._
_.- .. ''-. Redis 6.2.6 (00000000/0) 64 bit
.-.-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.-.|'_.-'| Port: 6379
|-. ._ / _.-' | PID: 14978-. -._-./ .-' .-'
|-._-. -.__.-' _.-'_.-'|
|-.-._ _.-'_.-' | https://redis.io-. -._-.__.-'.-' .-'
|-._-. -.__.-' _.-'_.-'|
|-.-._ _.-'_.-' |-. -._-..-'.-' .-'
-._-..-' _.-'
-._ _.-'-.__.-'
14978:S 24 Jan 2025 10:30:58.357 # Server initialized 14978:S 24 Jan 2025 10:30:58.357 * Loading RDB produced by version 6.2.6 14978:S 24 Jan 2025 10:30:58.357 * RDB age 0 seconds 14978:S 24 Jan 2025 10:30:58.357 * RDB memory usage when created 1.79 Mb 14978:S 24 Jan 2025 10:30:58.357 # Done loading RDB, keys loaded: 0, keys expired: 0. 14978:S 24 Jan 2025 10:30:58.357 * DB loaded from disk: 0.000 seconds 14978:S 24 Jan 2025 10:30:58.357 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer. 14978:S 24 Jan 2025 10:30:58.357 * Ready to accept connections 14978:S 24 Jan 2025 10:30:58.358 * Connecting to MASTER kc-redis01:6379 14978:S 24 Jan 2025 10:30:58.358 * MASTER <-> REPLICA sync started 14978:S 24 Jan 2025 10:30:58.359 * Non blocking connect for SYNC fired the event. 14978:S 24 Jan 2025 10:30:58.360 * Master replied to PING, replication can continue... 14978:S 24 Jan 2025 10:30:58.360 * Trying a partial resynchronization (request ccf6fe72648801a239e912ff4d33a75830037f32:1). 14978:S 24 Jan 2025 10:30:58.360 * Successful partial resynchronization with master. 14978:S 24 Jan 2025 10:30:58.360 * MASTER <-> REPLICA sync: Master accepted a Partial Resynchronization. 14978:S 24 Jan 2025 10:31:09.746 - Accepted 192.168.51.171:54724 14978:S 24 Jan 2025 10:31:09.747 - Client closed connection 14978:S 24 Jan 2025 10:31:17.166 - Accepted 192.168.51.160:60512 14978:S 24 Jan 2025 10:31:17.167 - Client closed connection 14978:S 24 Jan 2025 10:41:18.275 - Accepted 192.168.51.164:42943 14978:S 24 Jan 2025 10:41:18.276 - Accepted 192.168.51.164:58899 14978:S 24 Jan 2025 10:41:18.446 - Accepted 192.168.51.165:57275 14978:S 24 Jan 2025 10:41:18.446 - Accepted 192.168.51.165:55155 14978:S 24 Jan 2025 10:41:18.448 - Accepted 192.168.51.163:54867 14978:S 24 Jan 2025 10:41:18.448 - Accepted 192.168.51.163:45487 14978:S 24 Jan 2025 10:41:18.633 - Accepted 192.168.51.177:34181 14978:S 24 Jan 2025 10:41:18.634 - Accepted 192.168.51.177:49467 14978:S 24 Jan 2025 10:41:18.940 - Accepted 192.168.51.176:43379 14978:S 24 Jan 2025 10:41:18.940 - Accepted 192.168.51.176:55765 14978:S 24 Jan 2025 10:41:19.546 - Accepted 192.168.51.175:60931 14978:S 24 Jan 2025 10:41:19.546 - Accepted 192.168.51.175:42553 14978:S 24 Jan 2025 10:41:36.704 - Client closed connection 14978:S 24 Jan 2025 10:41:36.705 - Client closed connection 14978:S 24 Jan 2025 10:41:36.725 - Accepted 192.168.51.163:44213 14978:S 24 Jan 2025 10:41:36.725 - Accepted 192.168.51.163:54593 14978:S 24 Jan 2025 10:41:36.966 - Client closed connection 14978:S 24 Jan 2025 10:41:36.967 - Client closed connection 14978:S 24 Jan 2025 10:41:36.991 - Accepted 192.168.51.164:37893 14978:S 24 Jan 2025 10:41:36.991 - Accepted 192.168.51.164:40769 14978:S 24 Jan 2025 10:41:37.420 - Client closed connection 14978:S 24 Jan 2025 10:41:37.420 - Client closed connection 14978:S 24 Jan 2025 10:41:37.439 - Accepted 192.168.51.175:44977 14978:S 24 Jan 2025 10:41:37.439 - Accepted 192.168.51.175:59055 14978:S 24 Jan 2025 10:41:37.510 - Client closed connection 14978:S 24 Jan 2025 10:41:37.511 - Client closed connection 14978:S 24 Jan 2025 10:41:37.529 - Accepted 192.168.51.177:34867 14978:S 24 Jan 2025 10:41:37.529 - Accepted 192.168.51.177:51221 14978:S 24 Jan 2025 10:41:37.590 - Client closed connection 14978:S 24 Jan 2025 10:41:37.591 - Client closed connection 14978:S 24 Jan 2025 10:41:37.608 - Accepted 192.168.51.176:53315 14978:S 24 Jan 2025 10:41:37.608 - Accepted 192.168.51.176:47873 14978:S 24 Jan 2025 10:41:38.085 - Client closed connection 14978:S 24 Jan 2025 10:41:38.086 - Client closed connection 14978:S 24 Jan 2025 10:41:38.110 - Accepted 192.168.51.165:39163 14978:S 24 Jan 2025 10:41:38.110 - Accepted 192.168.51.165:41407 14978:M 24 Jan 2025 10:44:37.400 # Connection with master lost. 14978:M 24 Jan 2025 10:44:37.401 * Caching the disconnected master state. 14978:S 24 Jan 2025 10:44:37.401 * Connecting to MASTER 192.168.51.160:6379 14978:S 24 Jan 2025 10:44:37.401 * MASTER <-> REPLICA sync started 14978:S 24 Jan 2025 10:44:37.401 * REPLICAOF 192.168.51.160:6379 enabled (user request from 'id=18 addr=192.168.51.163:44213 laddr=192.168.51.171:6379 fd=13 name=sentinel-d09015fe-cmd age=181 idle=0 flags=x db=0 sub=0 psub=0 multi=4 qbuf=202 qbuf-free=40752 argv-mem=4 obl=45 oll=0 omem=0 tot-mem=61468 events=r cmd=exec user=default redir=-1') 14978:S 24 Jan 2025 10:44:37.403 # CONFIG REWRITE executed with success. 14978:S 24 Jan 2025 10:44:37.404 * Non blocking connect for SYNC fired the event. 14978:S 24 Jan 2025 10:44:37.404 * Master replied to PING, replication can continue... 14978:S 24 Jan 2025 10:44:37.404 * Trying a partial resynchronization (request ccf6fe72648801a239e912ff4d33a75830037f32:89318). 14978:S 24 Jan 2025 10:44:37.404 * Successful partial resynchronization with master. 14978:S 24 Jan 2025 10:44:37.404 * MASTER <-> REPLICA sync: Master accepted a Partial Resynchronization. 14978:S 24 Jan 2025 10:44:37.409 - Accepted 192.168.51.175:40501 14978:S 24 Jan 2025 10:44:37.409 - Accepted 192.168.51.175:42615 14978:S 24 Jan 2025 10:44:37.419 - Accepted 192.168.51.165:53115 14978:S 24 Jan 2025 10:44:37.419 - Accepted 192.168.51.165:53221 14978:S 24 Jan 2025 10:44:37.443 - Accepted 192.168.51.177:47457 14978:S 24 Jan 2025 10:44:37.443 - Accepted 192.168.51.177:45363 14978:S 24 Jan 2025 10:44:37.447 - Accepted 192.168.51.176:56899 14978:S 24 Jan 2025 10:44:37.447 - Accepted 192.168.51.176:52873 14978:S 24 Jan 2025 10:44:37.454 - Accepted 192.168.51.164:42011 14978:S 24 Jan 2025 10:44:37.454 - Accepted 192.168.51.164:49999 14978:S 24 Jan 2025 10:44:37.501 - Accepted 192.168.51.163:35797 14978:S 24 Jan 2025 11:05:08.136 - Client closed connection 14978:S 24 Jan 2025 11:05:08.136 # Connection with master lost. 14978:S 24 Jan 2025 11:05:08.136 * Caching the disconnected master state. 14978:S 24 Jan 2025 11:05:08.136 * Reconnecting to MASTER 192.168.51.160:6379 14978:S 24 Jan 2025 11:05:08.137 * MASTER <-> REPLICA sync started 14978:S 24 Jan 2025 11:05:08.137 - Accepted 192.168.51.160:35401 14978:S 24 Jan 2025 11:05:08.137 * Non blocking connect for SYNC fired the event. 14978:S 24 Jan 2025 11:05:08.138 * Master replied to PING, replication can continue... 14978:S 24 Jan 2025 11:05:08.138 * Trying a partial resynchronization (request ccf6fe72648801a239e912ff4d33a75830037f32:640976). 14978:S 24 Jan 2025 11:05:08.138 # Failover request received for replid ccf6fe72648801a239e912ff4d33a75830037f32. 14978:M 24 Jan 2025 11:05:08.138 * Discarding previously cached master state. 14978:M 24 Jan 2025 11:05:08.138 # Setting secondary replication ID to ccf6fe72648801a239e912ff4d33a75830037f32, valid up to offset: 640976. New replication ID is 30955f3561f21d7c9e62a9f890815e378db3b332 14978:M 24 Jan 2025 11:05:08.138 * MASTER MODE enabled (failover request from 'id=41 addr=192.168.51.160:35401 laddr=192.168.51.171:6379 fd=21 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=88 qbuf-free=40866 argv-mem=59 obl=0 oll=0 omem=0 tot-mem=61531 events=r cmd=psync user=default redir=-1') 14978:M 24 Jan 2025 11:05:08.138 * Replica 192.168.51.160:6379 asks for synchronization 14978:M 24 Jan 2025 11:05:08.139 * Partial resynchronization request from 192.168.51.160:6379 accepted. Sending 0 bytes of backlog starting from offset 640976. 14978:M 24 Jan 2025 11:06:03.763 - Client closed connection 14978:M 24 Jan 2025 11:06:03.763 - Client closed connection 14978:M 24 Jan 2025 11:06:03.763 - Client closed connection 14978:M 24 Jan 2025 11:06:03.763 - Reading from client: Connection reset by peer 14978:M 24 Jan 2025 11:06:03.764 - Client closed connection 14978:M 24 Jan 2025 11:06:03.764 - Reading from client: Connection reset by peer 14978:M 24 Jan 2025 11:06:03.764 - Client closed connection 14978:M 24 Jan 2025 11:06:03.764 - Reading from client: Connection reset by peer 14978:M 24 Jan 2025 11:06:03.764 - Client closed connection 14978:M 24 Jan 2025 11:06:03.764 - Reading from client: Connection reset by peer 14978:M 24 Jan 2025 11:06:03.769 - Accepted 192.168.51.165:48827 14978:M 24 Jan 2025 11:06:03.769 - Accepted 192.168.51.165:37853 14978:M 24 Jan 2025 11:06:03.785 - Accepted 192.168.51.177:59481 14978:M 24 Jan 2025 11:06:03.785 - Accepted 192.168.51.177:38787 14978:M 24 Jan 2025 11:06:03.802 - Accepted 192.168.51.175:49577 14978:M 24 Jan 2025 11:06:03.802 - Accepted 192.168.51.175:58939 14978:M 24 Jan 2025 11:06:03.824 - Accepted 192.168.51.164:58103 14978:M 24 Jan 2025 11:06:03.824 - Accepted 192.168.51.164:43775 14978:M 24 Jan 2025 11:06:03.832 - Accepted 192.168.51.176:35381 14978:M 24 Jan 2025 11:06:03.832 - Accepted 192.168.51.176:43747 14978:S 24 Jan 2025 11:06:06.871 # Connection with replica 192.168.51.160:6379 lost. 14978:S 24 Jan 2025 11:06:06.871 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer. 14978:S 24 Jan 2025 11:06:06.871 * Connecting to MASTER 192.168.51.161:6379 14978:S 24 Jan 2025 11:06:06.871 * MASTER <-> REPLICA sync started 14978:S 24 Jan 2025 11:06:06.871 * REPLICAOF 192.168.51.161:6379 enabled (user request from 'id=18 addr=192.168.51.163:44213 laddr=192.168.51.171:6379 fd=13 name=sentinel-d09015fe-cmd age=1470 idle=0 flags=x db=0 sub=0 psub=0 multi=4 qbuf=202 qbuf-free=40752 argv-mem=4 obl=45 oll=0 omem=0 tot-mem=61468 events=r cmd=exec user=default redir=-1') 14978:S 24 Jan 2025 11:06:06.874 # CONFIG REWRITE executed with success. 14978:S 24 Jan 2025 11:06:06.874 - Accepted 192.168.51.160:46705 14978:S 24 Jan 2025 11:06:06.874 * Non blocking connect for SYNC fired the event. 14978:S 24 Jan 2025 11:06:06.874 * Master replied to PING, replication can continue... 14978:S 24 Jan 2025 11:06:06.875 * Trying a partial resynchronization (request 30955f3561f21d7c9e62a9f890815e378db3b332:666923). 14978:S 24 Jan 2025 11:06:06.875 - Client closed connection 14978:S 24 Jan 2025 11:06:06.876 * Full resync from master: b593051fad65a8c04dd061a548bf955abacfd00f:667318 14978:S 24 Jan 2025 11:06:06.876 * Discarding previously cached master state. 14978:S 24 Jan 2025 11:06:06.892 - Accepted 192.168.51.177:51981 14978:S 24 Jan 2025 11:06:06.892 - Accepted 192.168.51.177:39637 14978:S 24 Jan 2025 11:06:06.894 - Accepted 192.168.51.175:47755 14978:S 24 Jan 2025 11:06:06.894 - Accepted 192.168.51.175:38487 14978:S 24 Jan 2025 11:06:06.909 - Accepted 192.168.51.165:58293 14978:S 24 Jan 2025 11:06:06.909 - Accepted 192.168.51.165:46781 14978:S 24 Jan 2025 11:06:06.912 - Accepted 192.168.51.164:59305 14978:S 24 Jan 2025 11:06:06.912 - Accepted 192.168.51.164:42539 14978:S 24 Jan 2025 11:06:06.932 * MASTER <-> REPLICA sync: receiving 178 bytes from master to disk 14978:S 24 Jan 2025 11:06:06.932 * MASTER <-> REPLICA sync: Flushing old data 14978:S 24 Jan 2025 11:06:06.932 * MASTER <-> REPLICA sync: Loading DB in memory 14978:S 24 Jan 2025 11:06:06.934 * Loading RDB produced by version 6.2.6 14978:S 24 Jan 2025 11:06:06.934 * RDB age 0 seconds 14978:S 24 Jan 2025 11:06:06.934 * RDB memory usage when created 2.13 Mb 14978:S 24 Jan 2025 11:06:06.934 # Done loading RDB, keys loaded: 0, keys expired: 0. 14978:S 24 Jan 2025 11:06:06.934 * MASTER <-> REPLICA sync: Finished with success 14978:S 24 Jan 2025 11:06:06.955 - Accepted 192.168.51.163:49509 14978:S 24 Jan 2025 11:06:06.963 - Accepted 192.168.51.176:34099 14978:S 24 Jan 2025 11:06:06.963 - Accepted 192.168.51.176:40471 14978:S 24 Jan 2025 11:06:07.623 - Accepted 192.168.51.160:45629 14978:S 24 Jan 2025 11:06:07.624 * Replica 192.168.51.160:6379 asks for synchronization 14978:S 24 Jan 2025 11:06:07.624 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for '30955f3561f21d7c9e62a9f890815e378db3b332', my replication IDs are 'b593051fad65a8c04dd061a548bf955abacfd00f' and '0000000000000000000000000000000000000000') 14978:S 24 Jan 2025 11:06:07.624 * Starting BGSAVE for SYNC with target: disk 14978:S 24 Jan 2025 11:06:07.625 * Background saving started by pid 20658 20658:C 24 Jan 2025 11:06:07.626 * DB saved on disk 20658:C 24 Jan 2025 11:06:07.626 * RDB: 0 MB of memory used by copy-on-write 14978:S 24 Jan 2025 11:06:07.706 * Background saving terminated with success 14978:S 24 Jan 2025 11:06:07.706 * Synchronization with replica 192.168.51.160:6379 succeeded 14978:S 24 Jan 2025 11:06:07.924 - Client closed connection 14978:S 24 Jan 2025 11:06:07.924 - Client closed connection 14978:S 24 Jan 2025 11:06:07.983 - Accepted 192.168.51.163:36181 14978:S 24 Jan 2025 11:06:07.983 - Accepted 192.168.51.163:43937 14978:S 24 Jan 2025 11:09:04.322 - Client closed connection 14978:S 24 Jan 2025 11:09:04.323 # Connection with replica 192.168.51.160:6379 lost. 14978:S 24 Jan 2025 11:18:13.005 - Accepted 172.16.15.134:43622 14978:S 24 Jan 2025 11:18:13.058 - Client closed connection
log from redis01 15140:M 24 Jan 2025 10:30:58.115 # Server initialized 15140:M 24 Jan 2025 10:30:58.115 * Loading RDB produced by version 6.2.6 15140:M 24 Jan 2025 10:30:58.115 * RDB age 0 seconds 15140:M 24 Jan 2025 10:30:58.115 * RDB memory usage when created 1.87 Mb 15140:M 24 Jan 2025 10:30:58.115 # Done loading RDB, keys loaded: 0, keys expired: 0. 15140:M 24 Jan 2025 10:30:58.115 * DB loaded from disk: 0.000 seconds 15140:M 24 Jan 2025 10:30:58.115 * Ready to accept connections 15140:M 24 Jan 2025 10:30:58.236 - Accepted 192.168.51.171:33311 15140:M 24 Jan 2025 10:30:58.237 * Replica 192.168.51.171:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.237 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'fe4ee1c081ee5d3e4fbd289fcf47698757bcf963', my replication IDs are '44157daec5c490a80c7054130353711ef8cec4d0' and '0000000000000000000000000000000000000000') 15140:M 24 Jan 2025 10:30:58.237 * Replication backlog created, my new replication IDs are 'ccf6fe72648801a239e912ff4d33a75830037f32' and '0000000000000000000000000000000000000000' 15140:M 24 Jan 2025 10:30:58.237 * Starting BGSAVE for SYNC with target: disk 15140:M 24 Jan 2025 10:30:58.238 * Background saving started by pid 15162 15162:C 24 Jan 2025 10:30:58.240 * DB saved on disk 15162:C 24 Jan 2025 10:30:58.241 * RDB: 0 MB of memory used by copy-on-write 15140:M 24 Jan 2025 10:30:58.248 - Accepted 192.168.51.173:40689 15140:M 24 Jan 2025 10:30:58.248 * Replica 192.168.51.173:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.248 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'fe4ee1c081ee5d3e4fbd289fcf47698757bcf963', my replication IDs are 'ccf6fe72648801a239e912ff4d33a75830037f32' and '0000000000000000000000000000000000000000') 15140:M 24 Jan 2025 10:30:58.248 * Waiting for end of BGSAVE for SYNC 15140:M 24 Jan 2025 10:30:58.318 * Background saving terminated with success 15140:M 24 Jan 2025 10:30:58.318 * Synchronization with replica 192.168.51.171:6379 succeeded 15140:M 24 Jan 2025 10:30:58.319 * Synchronization with replica 192.168.51.173:6379 succeeded 15140:M 24 Jan 2025 10:30:58.339 - Client closed connection 15140:M 24 Jan 2025 10:30:58.339 # Connection with replica 192.168.51.171:6379 lost. 15140:M 24 Jan 2025 10:30:58.359 - Accepted 192.168.51.171:37905 15140:M 24 Jan 2025 10:30:58.360 * Replica 192.168.51.171:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.360 * Partial resynchronization request from 192.168.51.171:6379 accepted. Sending 0 bytes of backlog starting from offset 1. 15140:M 24 Jan 2025 10:30:58.375 - Accepted 192.168.51.172:46159 15140:M 24 Jan 2025 10:30:58.377 * Replica 192.168.51.172:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.377 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'fe4ee1c081ee5d3e4fbd289fcf47698757bcf963', my replication IDs are 'ccf6fe72648801a239e912ff4d33a75830037f32' and '0000000000000000000000000000000000000000') 15140:M 24 Jan 2025 10:30:58.377 * Starting BGSAVE for SYNC with target: disk 15140:M 24 Jan 2025 10:30:58.378 * Background saving started by pid 15163 15163:C 24 Jan 2025 10:30:58.380 * DB saved on disk 15163:C 24 Jan 2025 10:30:58.381 * RDB: 0 MB of memory used by copy-on-write 15140:M 24 Jan 2025 10:30:58.419 * Background saving terminated with success 15140:M 24 Jan 2025 10:30:58.419 * Synchronization with replica 192.168.51.172:6379 succeeded 15140:M 24 Jan 2025 10:30:58.479 - Client closed connection 15140:M 24 Jan 2025 10:30:58.479 # Connection with replica 192.168.51.172:6379 lost. 15140:M 24 Jan 2025 10:30:58.502 - Accepted 192.168.51.172:45555 15140:M 24 Jan 2025 10:30:58.502 * Replica 192.168.51.172:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.502 * Partial resynchronization request from 192.168.51.172:6379 accepted. Sending 0 bytes of backlog starting from offset 1. 15140:M 24 Jan 2025 10:30:58.552 - Client closed connection 15140:M 24 Jan 2025 10:30:58.553 # Connection with replica 192.168.51.173:6379 lost. 15140:M 24 Jan 2025 10:30:58.586 - Accepted 192.168.51.173:36093 15140:M 24 Jan 2025 10:30:58.586 * Replica 192.168.51.173:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.587 * Partial resynchronization request from 192.168.51.173:6379 accepted. Sending 0 bytes of backlog starting from offset 1. 15140:M 24 Jan 2025 10:30:58.819 - Accepted 192.168.51.162:38771 15140:M 24 Jan 2025 10:30:58.820 * Replica 192.168.51.162:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.820 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'fe4ee1c081ee5d3e4fbd289fcf47698757bcf963', my replication IDs are 'ccf6fe72648801a239e912ff4d33a75830037f32' and '0000000000000000000000000000000000000000') 15140:M 24 Jan 2025 10:30:58.820 * Starting BGSAVE for SYNC with target: disk 15140:M 24 Jan 2025 10:30:58.820 * Background saving started by pid 15169 15169:C 24 Jan 2025 10:30:58.822 * DB saved on disk 15169:C 24 Jan 2025 10:30:58.823 * RDB: 0 MB of memory used by copy-on-write 15140:M 24 Jan 2025 10:30:58.888 - Accepted 192.168.51.161:41719 15140:M 24 Jan 2025 10:30:58.888 * Replica 192.168.51.161:6379 asks for synchronization 15140:M 24 Jan 2025 10:30:58.888 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'fe4ee1c081ee5d3e4fbd289fcf47698757bcf963', my replication IDs are 'ccf6fe72648801a239e912ff4d33a75830037f32' and '0000000000000000000000000000000000000000') 15140:M 24 Jan 2025 10:30:58.888 * Waiting for end of BGSAVE for SYNC 15140:M 24 Jan 2025 10:30:58.923 * Background saving terminated with success 15140:M 24 Jan 2025 10:30:58.923 * Synchronization with replica 192.168.51.162:6379 succeeded 15140:M 24 Jan 2025 10:30:58.923 * Synchronization with replica 192.168.51.161:6379 succeeded 15140:M 24 Jan 2025 10:31:09.383 - Accepted 192.168.51.160:52830 15140:M 24 Jan 2025 10:31:09.384 - Client closed connection 15140:M 24 Jan 2025 10:31:12.425 - Accepted 192.168.51.160:52832 15140:M 24 Jan 2025 10:31:12.426 - Client closed connection 15140:M 24 Jan 2025 10:35:01.021 - Accepted 192.168.51.160:40724 15140:M 24 Jan 2025 10:35:01.025 - Client closed connection 15140:M 24 Jan 2025 10:35:31.020 - Accepted 192.168.51.160:49994 15140:M 24 Jan 2025 10:35:31.025 - Client closed connection 15140:M 24 Jan 2025 10:36:01.018 - Accepted 192.168.51.160:41140 15140:M 24 Jan 2025 10:36:01.020 - Client closed connection 15140:M 24 Jan 2025 10:36:31.018 - Accepted 192.168.51.160:38078 15140:M 24 Jan 2025 10:36:31.020 - Client closed connection 15140:M 24 Jan 2025 10:37:01.018 - Accepted 192.168.51.160:54484 15140:M 24 Jan 2025 10:37:01.020 - Client closed connection 15140:M 24 Jan 2025 10:37:31.018 - Accepted 192.168.51.160:34632 15140:M 24 Jan 2025 10:37:31.022 - Client closed connection 15140:M 24 Jan 2025 10:38:01.019 - Accepted 192.168.51.160:47922 15140:M 24 Jan 2025 10:38:01.024 - Client closed connection 15140:M 24 Jan 2025 10:38:31.019 - Accepted 192.168.51.160:53836 15140:M 24 Jan 2025 10:38:31.024 - Client closed connection 15140:M 24 Jan 2025 10:39:01.020 - Accepted 192.168.51.160:45910 15140:M 24 Jan 2025 10:39:01.024 - Client closed connection 15140:M 24 Jan 2025 10:39:31.018 - Accepted 192.168.51.160:35058 15140:M 24 Jan 2025 10:39:31.021 - Client closed connection 15140:M 24 Jan 2025 10:40:01.019 - Accepted 192.168.51.160:59866 15140:M 24 Jan 2025 10:40:01.020 - Client closed connection 15140:M 24 Jan 2025 10:40:31.019 - Accepted 192.168.51.160:52478 15140:M 24 Jan 2025 10:40:31.020 - Client closed connection 15140:M 24 Jan 2025 10:41:01.019 - Accepted 192.168.51.160:49088 15140:M 24 Jan 2025 10:41:01.024 - Client closed connection 15140:M 24 Jan 2025 10:41:18.223 - Accepted 192.168.51.164:59417 15140:M 24 Jan 2025 10:41:18.223 - Accepted 192.168.51.164:33769 15140:M 24 Jan 2025 10:41:18.347 - Accepted 192.168.51.163:57123 15140:M 24 Jan 2025 10:41:18.347 - Accepted 192.168.51.163:40291 15140:M 24 Jan 2025 10:41:18.362 - Accepted 192.168.51.165:52437 15140:M 24 Jan 2025 10:41:18.362 - Accepted 192.168.51.165:40269 15140:M 24 Jan 2025 10:41:18.570 - Accepted 192.168.51.177:50245 15140:M 24 Jan 2025 10:41:18.570 - Accepted 192.168.51.177:57485 15140:M 24 Jan 2025 10:41:18.863 - Accepted 192.168.51.176:60085 15140:M 24 Jan 2025 10:41:18.863 - Accepted 192.168.51.176:46145 15140:M 24 Jan 2025 10:41:19.490 - Accepted 192.168.51.175:46599 15140:M 24 Jan 2025 10:41:19.490 - Accepted 192.168.51.175:56813 15140:M 24 Jan 2025 10:41:31.019 - Accepted 192.168.51.160:57668 15140:M 24 Jan 2025 10:41:31.023 - Client closed connection 15140:M 24 Jan 2025 10:41:36.705 - Client closed connection 15140:M 24 Jan 2025 10:41:36.705 - Client closed connection 15140:M 24 Jan 2025 10:41:36.725 - Accepted 192.168.51.163:42901 15140:M 24 Jan 2025 10:41:36.725 - Accepted 192.168.51.163:56633 15140:M 24 Jan 2025 10:41:36.967 - Client closed connection 15140:M 24 Jan 2025 10:41:36.967 - Client closed connection 15140:M 24 Jan 2025 10:41:36.991 - Accepted 192.168.51.164:58237 15140:M 24 Jan 2025 10:41:36.991 - Accepted 192.168.51.164:39357 15140:M 24 Jan 2025 10:41:37.420 - Client closed connection 15140:M 24 Jan 2025 10:41:37.420 - Client closed connection 15140:M 24 Jan 2025 10:41:37.439 - Accepted 192.168.51.175:58277 15140:M 24 Jan 2025 10:41:37.439 - Accepted 192.168.51.175:34297 15140:M 24 Jan 2025 10:41:37.510 - Client closed connection 15140:M 24 Jan 2025 10:41:37.510 - Client closed connection 15140:M 24 Jan 2025 10:41:37.529 - Accepted 192.168.51.177:49665 15140:M 24 Jan 2025 10:41:37.529 - Accepted 192.168.51.177:38585 15140:M 24 Jan 2025 10:41:37.591 - Client closed connection 15140:M 24 Jan 2025 10:41:37.591 - Client closed connection 15140:M 24 Jan 2025 10:41:37.608 - Accepted 192.168.51.176:39447 15140:M 24 Jan 2025 10:41:37.608 - Accepted 192.168.51.176:44745 15140:M 24 Jan 2025 10:41:38.085 - Client closed connection 15140:M 24 Jan 2025 10:41:38.085 - Client closed connection 15140:M 24 Jan 2025 10:41:38.110 - Accepted 192.168.51.165:59093 15140:M 24 Jan 2025 10:41:38.110 - Accepted 192.168.51.165:43555 15140:M 24 Jan 2025 10:42:01.018 - Accepted 192.168.51.160:49764 15140:M 24 Jan 2025 10:42:01.022 - Client closed connection 15140:M 24 Jan 2025 10:42:31.018 - Accepted 192.168.51.160:44158 15140:M 24 Jan 2025 10:42:31.023 - Client closed connection 15140:M 24 Jan 2025 10:43:01.021 - Accepted 192.168.51.160:33136 15140:M 24 Jan 2025 10:43:01.025 - Client closed connection 15140:M 24 Jan 2025 10:43:31.019 - Accepted 192.168.51.160:52254 15140:M 24 Jan 2025 10:43:31.020 - Client closed connection 15140:M 24 Jan 2025 10:44:01.019 - Accepted 192.168.51.160:58430 15140:M 24 Jan 2025 10:44:01.020 - Client closed connection 15140:M 24 Jan 2025 10:44:31.018 - Accepted 192.168.51.160:56612 15140:M 24 Jan 2025 10:44:31.020 - Client closed connection 15140:M 24 Jan 2025 10:44:37.400 - Client closed connection 15140:M 24 Jan 2025 10:44:37.400 # Connection with replica 192.168.51.172:6379 lost. 15140:M 24 Jan 2025 10:44:37.401 - Accepted 192.168.51.172:34095 15140:M 24 Jan 2025 10:44:37.401 - Client closed connection 15140:M 24 Jan 2025 10:44:37.401 # Connection with replica 192.168.51.162:6379 lost. 15140:M 24 Jan 2025 10:44:37.401 - Client closed connection 15140:M 24 Jan 2025 10:44:37.401 - Client closed connection 15140:M 24 Jan 2025 10:44:37.401 # Connection with replica 192.168.51.173:6379 lost. 15140:M 24 Jan 2025 10:44:37.401 # Connection with replica 192.168.51.171:6379 lost. 15140:M 24 Jan 2025 10:44:37.401 - Accepted 192.168.51.162:44777 15140:M 24 Jan 2025 10:44:37.401 - Accepted 192.168.51.171:40291 15140:M 24 Jan 2025 10:44:37.401 - Accepted 192.168.51.173:33509 15140:M 24 Jan 2025 10:44:37.402 - Client closed connection 15140:M 24 Jan 2025 10:44:37.402 # Connection with replica 192.168.51.161:6379 lost. 15140:M 24 Jan 2025 10:44:37.402 - Accepted 192.168.51.161:39525 15140:M 24 Jan 2025 10:44:37.403 * Replica 192.168.51.172:6379 asks for synchronization 15140:M 24 Jan 2025 10:44:37.403 * Partial resynchronization request from 192.168.51.172:6379 accepted. Sending 0 bytes of backlog starting from offset 89318. 15140:M 24 Jan 2025 10:44:37.404 * Replica 192.168.51.173:6379 asks for synchronization 15140:M 24 Jan 2025 10:44:37.404 * Partial resynchronization request from 192.168.51.173:6379 accepted. Sending 0 bytes of backlog starting from offset 89318. 15140:M 24 Jan 2025 10:44:37.404 * Replica 192.168.51.162:6379 asks for synchronization 15140:M 24 Jan 2025 10:44:37.404 * Partial resynchronization request from 192.168.51.162:6379 accepted. Sending 0 bytes of backlog starting from offset 89318. 15140:M 24 Jan 2025 10:44:37.404 * Replica 192.168.51.171:6379 asks for synchronization 15140:M 24 Jan 2025 10:44:37.404 * Partial resynchronization request from 192.168.51.171:6379 accepted. Sending 0 bytes of backlog starting from offset 89318. 15140:M 24 Jan 2025 10:44:37.408 * Replica 192.168.51.161:6379 asks for synchronization 15140:M 24 Jan 2025 10:44:37.408 * Partial resynchronization request from 192.168.51.161:6379 accepted. Sending 0 bytes of backlog starting from offset 89318. 15140:M 24 Jan 2025 10:45:01.019 - Accepted 192.168.51.160:46966 15140:M 24 Jan 2025 10:45:01.024 - Client closed connection 15140:M 24 Jan 2025 10:45:31.018 - Accepted 192.168.51.160:46120 15140:M 24 Jan 2025 10:45:31.022 - Client closed connection 15140:M 24 Jan 2025 10:46:01.019 - Accepted 192.168.51.160:34790 15140:M 24 Jan 2025 10:46:01.024 - Client closed connection 15140:M 24 Jan 2025 10:46:31.018 - Accepted 192.168.51.160:57530 15140:M 24 Jan 2025 10:46:31.020 - Client closed connection 15140:M 24 Jan 2025 10:47:01.019 - Accepted 192.168.51.160:58372 15140:M 24 Jan 2025 10:47:01.024 - Client closed connection 15140:M 24 Jan 2025 10:47:31.019 - Accepted 192.168.51.160:58632 15140:M 24 Jan 2025 10:47:31.023 - Client closed connection 15140:M 24 Jan 2025 10:48:01.018 - Accepted 192.168.51.160:59436 15140:M 24 Jan 2025 10:48:01.019 - Client closed connection 15140:M 24 Jan 2025 10:48:31.019 - Accepted 192.168.51.160:53260 15140:M 24 Jan 2025 10:48:31.021 - Client closed connection 15140:M 24 Jan 2025 10:49:01.018 - Accepted 192.168.51.160:42372 15140:M 24 Jan 2025 10:49:01.021 - Client closed connection 15140:M 24 Jan 2025 10:49:31.018 - Accepted 192.168.51.160:56446 15140:M 24 Jan 2025 10:49:31.020 - Client closed connection 15140:M 24 Jan 2025 10:50:01.019 - Accepted 192.168.51.160:39740 15140:M 24 Jan 2025 10:50:01.024 - Client closed connection 15140:M 24 Jan 2025 10:50:31.018 - Accepted 192.168.51.160:49794 15140:M 24 Jan 2025 10:50:31.020 - Client closed connection 15140:M 24 Jan 2025 10:51:01.018 - Accepted 192.168.51.160:50588 15140:M 24 Jan 2025 10:51:01.020 - Client closed connection 15140:M 24 Jan 2025 10:51:31.022 - Accepted 192.168.51.160:49222 15140:M 24 Jan 2025 10:51:31.025 - Client closed connection 15140:M 24 Jan 2025 10:52:01.018 - Accepted 192.168.51.160:60614 15140:M 24 Jan 2025 10:52:01.023 - Client closed connection 15140:M 24 Jan 2025 10:52:31.018 - Accepted 192.168.51.160:36376 15140:M 24 Jan 2025 10:52:31.022 - Client closed connection 15140:M 24 Jan 2025 10:53:01.018 - Accepted 192.168.51.160:50796 15140:M 24 Jan 2025 10:53:01.020 - Client closed connection 15140:M 24 Jan 2025 10:53:31.018 - Accepted 192.168.51.160:34780 15140:M 24 Jan 2025 10:53:31.022 - Client closed connection 15140:M 24 Jan 2025 10:54:01.019 - Accepted 192.168.51.160:53086 15140:M 24 Jan 2025 10:54:01.023 - Client closed connection 15140:M 24 Jan 2025 10:54:31.018 - Accepted 192.168.51.160:58464 15140:M 24 Jan 2025 10:54:31.022 - Client closed connection 15140:M 24 Jan 2025 10:55:01.018 - Accepted 192.168.51.160:47378 15140:M 24 Jan 2025 10:55:01.021 - Client closed connection 15140:M 24 Jan 2025 10:55:31.018 - Accepted 192.168.51.160:46924 15140:M 24 Jan 2025 10:55:31.020 - Client closed connection 15140:M 24 Jan 2025 10:56:01.018 - Accepted 192.168.51.160:49828 15140:M 24 Jan 2025 10:56:01.020 - Client closed connection 15140:M 24 Jan 2025 10:56:31.018 - Accepted 192.168.51.160:43138 15140:M 24 Jan 2025 10:56:31.020 - Client closed connection 15140:M 24 Jan 2025 10:57:01.019 - Accepted 192.168.51.160:50376 15140:M 24 Jan 2025 10:57:01.023 - Client closed connection 15140:M 24 Jan 2025 10:57:31.018 - Accepted 192.168.51.160:33066 15140:M 24 Jan 2025 10:57:31.021 - Client closed connection 15140:M 24 Jan 2025 10:58:01.019 - Accepted 192.168.51.160:40500 15140:M 24 Jan 2025 10:58:01.023 - Client closed connection 15140:M 24 Jan 2025 10:58:31.019 - Accepted 192.168.51.160:48364 15140:M 24 Jan 2025 10:58:31.021 - Client closed connection 15140:M 24 Jan 2025 10:59:01.018 - Accepted 192.168.51.160:36892 15140:M 24 Jan 2025 10:59:01.020 - Client closed connection 15140:M 24 Jan 2025 10:59:31.018 - Accepted 192.168.51.160:41218 15140:M 24 Jan 2025 10:59:31.022 - Client closed connection 15140:M 24 Jan 2025 11:00:01.018 - Accepted 192.168.51.160:46552 15140:M 24 Jan 2025 11:00:01.020 - Client closed connection 15140:M 24 Jan 2025 11:00:31.018 - Accepted 192.168.51.160:33536 15140:M 24 Jan 2025 11:00:31.021 - Client closed connection 15140:M 24 Jan 2025 11:01:01.018 - Accepted 192.168.51.160:50596 15140:M 24 Jan 2025 11:01:01.020 - Client closed connection 15140:M 24 Jan 2025 11:01:31.018 - Accepted 192.168.51.160:59318 15140:M 24 Jan 2025 11:01:31.021 - Client closed connection 15140:M 24 Jan 2025 11:02:01.020 - Accepted 192.168.51.160:44256 15140:M 24 Jan 2025 11:02:01.023 - Client closed connection 15140:M 24 Jan 2025 11:02:31.019 - Accepted 192.168.51.160:50700 15140:M 24 Jan 2025 11:02:31.021 - Client closed connection 15140:M 24 Jan 2025 11:03:01.018 - Accepted 192.168.51.160:46142 15140:M 24 Jan 2025 11:03:01.021 - Client closed connection 15140:M 24 Jan 2025 11:03:31.019 - Accepted 192.168.51.160:49236 15140:M 24 Jan 2025 11:03:31.021 - Client closed connection 15140:M 24 Jan 2025 11:04:01.018 - Accepted 192.168.51.160:58352 15140:M 24 Jan 2025 11:04:01.021 - Client closed connection 15140:M 24 Jan 2025 11:04:31.018 - Accepted 192.168.51.160:57128 15140:M 24 Jan 2025 11:04:31.022 - Client closed connection 15140:M 24 Jan 2025 11:04:31.108 - Accepted 172.16.15.134:55034 15140:M 24 Jan 2025 11:04:31.153 - Client closed connection 15140:M 24 Jan 2025 11:04:43.610 - Accepted 172.16.15.134:42998 15140:M 24 Jan 2025 11:04:43.665 - Client closed connection 15140:M 24 Jan 2025 11:05:01.018 - Accepted 192.168.51.160:44416 15140:M 24 Jan 2025 11:05:01.020 - Client closed connection 15140:M 24 Jan 2025 11:05:07.394 - Accepted 172.16.15.134:58678 15140:M 24 Jan 2025 11:05:07.420 * FAILOVER requested to 192.168.51.171:6379. 15140:M 24 Jan 2025 11:05:07.442 - Client closed connection 15140:M 24 Jan 2025 11:05:08.135 * Failover target 192.168.51.171:6379 is synced, failing over. 15140:S 24 Jan 2025 11:05:08.135 # Connection with replica 192.168.51.172:6379 lost. 15140:S 24 Jan 2025 11:05:08.136 # Connection with replica 192.168.51.173:6379 lost. 15140:S 24 Jan 2025 11:05:08.136 # Connection with replica 192.168.51.162:6379 lost. 15140:S 24 Jan 2025 11:05:08.136 # Connection with replica 192.168.51.171:6379 lost. 15140:S 24 Jan 2025 11:05:08.136 # Connection with replica 192.168.51.161:6379 lost. 15140:S 24 Jan 2025 11:05:08.136 * Before turning into a replica, using my own master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partial transfer. 15140:S 24 Jan 2025 11:05:08.136 * Connecting to MASTER 192.168.51.171:6379 15140:S 24 Jan 2025 11:05:08.136 * MASTER <-> REPLICA sync started 15140:S 24 Jan 2025 11:05:08.137 - Accepted 192.168.51.161:36791 15140:S 24 Jan 2025 11:05:08.137 - Accepted 192.168.51.173:34459 15140:S 24 Jan 2025 11:05:08.137 * Non blocking connect for SYNC fired the event. 15140:S 24 Jan 2025 11:05:08.137 - Accepted 192.168.51.172:43851 15140:S 24 Jan 2025 11:05:08.137 - Accepted 192.168.51.162:40787 15140:S 24 Jan 2025 11:05:08.137 - Accepted 192.168.51.171:41675 15140:S 24 Jan 2025 11:05:08.137 * Master replied to PING, replication can continue... 15140:S 24 Jan 2025 11:05:08.138 * Trying a partial resynchronization (request ccf6fe72648801a239e912ff4d33a75830037f32:640976). 15140:S 24 Jan 2025 11:05:08.138 - Client closed connection 15140:S 24 Jan 2025 11:05:08.139 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:05:08.139 - Client closed connection 15140:S 24 Jan 2025 11:05:08.139 - Client closed connection 15140:S 24 Jan 2025 11:05:08.139 * Successful partial resynchronization with master. 15140:S 24 Jan 2025 11:05:08.139 # Master replication ID changed to 30955f3561f21d7c9e62a9f890815e378db3b332 15140:S 24 Jan 2025 11:05:08.139 * MASTER <-> REPLICA sync: Master accepted a Partial Resynchronization. 15140:S 24 Jan 2025 11:05:08.139 * Replica 192.168.51.162:6379 asks for synchronization 15140:S 24 Jan 2025 11:05:08.139 * Partial resynchronization request from 192.168.51.162:6379 accepted. Sending 0 bytes of backlog starting from offset 640976. 15140:S 24 Jan 2025 11:05:08.784 - Accepted 192.168.51.172:37467 15140:S 24 Jan 2025 11:05:08.785 * Replica 192.168.51.172:6379 asks for synchronization 15140:S 24 Jan 2025 11:05:08.785 * Partial resynchronization request from 192.168.51.172:6379 accepted. Sending 175 bytes of backlog starting from offset 640976. 15140:S 24 Jan 2025 11:05:08.830 - Accepted 192.168.51.173:34821 15140:S 24 Jan 2025 11:05:08.831 * Replica 192.168.51.173:6379 asks for synchronization 15140:S 24 Jan 2025 11:05:08.831 * Partial resynchronization request from 192.168.51.173:6379 accepted. Sending 175 bytes of backlog starting from offset 640976. 15140:S 24 Jan 2025 11:05:09.065 - Accepted 192.168.51.161:43815 15140:S 24 Jan 2025 11:05:09.066 * Replica 192.168.51.161:6379 asks for synchronization 15140:S 24 Jan 2025 11:05:09.066 * Partial resynchronization request from 192.168.51.161:6379 accepted. Sending 479 bytes of backlog starting from offset 640976. 15140:S 24 Jan 2025 11:05:31.018 - Accepted 192.168.51.160:52226 15140:S 24 Jan 2025 11:05:31.021 - Client closed connection 15140:S 24 Jan 2025 11:06:01.018 - Accepted 192.168.51.160:44620 15140:S 24 Jan 2025 11:06:01.022 - Client closed connection 15140:S 24 Jan 2025 11:06:02.796 - Client closed connection 15140:S 24 Jan 2025 11:06:02.796 # Connection with replica 192.168.51.161:6379 lost. 15140:S 24 Jan 2025 11:06:03.763 - Client closed connection 15140:S 24 Jan 2025 11:06:03.764 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:06:03.764 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:06:03.764 - Client closed connection 15140:S 24 Jan 2025 11:06:03.764 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:06:03.764 - Client closed connection 15140:S 24 Jan 2025 11:06:03.764 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:06:03.764 # Connection with replica client id #112 lost. 15140:S 24 Jan 2025 11:06:03.765 - Client closed connection 15140:S 24 Jan 2025 11:06:03.765 - Client closed connection 15140:S 24 Jan 2025 11:06:03.765 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:06:03.765 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:06:03.770 - Accepted 192.168.51.165:47479 15140:S 24 Jan 2025 11:06:03.770 - Accepted 192.168.51.165:51635 15140:S 24 Jan 2025 11:06:03.785 - Accepted 192.168.51.177:47693 15140:S 24 Jan 2025 11:06:03.785 - Accepted 192.168.51.177:49315 15140:S 24 Jan 2025 11:06:03.803 - Accepted 192.168.51.175:42137 15140:S 24 Jan 2025 11:06:03.803 - Accepted 192.168.51.175:42087 15140:S 24 Jan 2025 11:06:03.824 - Accepted 192.168.51.164:56005 15140:S 24 Jan 2025 11:06:03.824 - Accepted 192.168.51.164:52215 15140:S 24 Jan 2025 11:06:03.832 - Accepted 192.168.51.176:47053 15140:S 24 Jan 2025 11:06:03.832 - Accepted 192.168.51.176:33957 15140:S 24 Jan 2025 11:06:04.735 - Client closed connection 15140:S 24 Jan 2025 11:06:04.735 # Connection with replica 192.168.51.162:6379 lost. 15140:S 24 Jan 2025 11:06:05.805 - Reading from client: Connection reset by peer 15140:S 24 Jan 2025 11:06:05.805 # Connection with replica client id #113 lost. 15140:S 24 Jan 2025 11:06:06.871 - Client closed connection 15140:S 24 Jan 2025 11:06:06.872 # Connection with master lost. 15140:S 24 Jan 2025 11:06:06.872 * Caching the disconnected master state. 15140:S 24 Jan 2025 11:06:06.872 * Reconnecting to MASTER 192.168.51.171:6379 15140:S 24 Jan 2025 11:06:06.872 * MASTER <-> REPLICA sync started 15140:S 24 Jan 2025 11:06:06.872 * Non blocking connect for SYNC fired the event. 15140:S 24 Jan 2025 11:06:06.875 * Master replied to PING, replication can continue... 15140:S 24 Jan 2025 11:06:06.875 * Trying a partial resynchronization (request 30955f3561f21d7c9e62a9f890815e378db3b332:666923). 15140:S 24 Jan 2025 11:06:06.875 * Master is currently unable to PSYNC but should be in the future: -NOMASTERLINK Can't SYNC while not connected with my master 15140:S 24 Jan 2025 11:06:07.623 * Connecting to MASTER 192.168.51.171:6379 15140:S 24 Jan 2025 11:06:07.623 * MASTER <-> REPLICA sync started 15140:S 24 Jan 2025 11:06:07.623 * Non blocking connect for SYNC fired the event. 15140:S 24 Jan 2025 11:06:07.624 * Master replied to PING, replication can continue... 15140:S 24 Jan 2025 11:06:07.624 * Trying a partial resynchronization (request 30955f3561f21d7c9e62a9f890815e378db3b332:666923). 15140:S 24 Jan 2025 11:06:07.625 * Full resync from master: b593051fad65a8c04dd061a548bf955abacfd00f:667797 15140:S 24 Jan 2025 11:06:07.625 * Discarding previously cached master state. 15140:S 24 Jan 2025 11:06:07.707 * MASTER <-> REPLICA sync: receiving 178 bytes from master to disk 15140:S 24 Jan 2025 11:06:07.707 * MASTER <-> REPLICA sync: Flushing old data 15140:S 24 Jan 2025 11:06:07.707 * MASTER <-> REPLICA sync: Loading DB in memory 15140:S 24 Jan 2025 11:06:07.709 * Loading RDB produced by version 6.2.6 15140:S 24 Jan 2025 11:06:07.709 * RDB age 0 seconds 15140:S 24 Jan 2025 11:06:07.709 * RDB memory usage when created 2.09 Mb 15140:S 24 Jan 2025 11:06:07.709 # Done loading RDB, keys loaded: 0, keys expired: 0. 15140:S 24 Jan 2025 11:06:07.709 * MASTER <-> REPLICA sync: Finished with success 15140:S 24 Jan 2025 11:06:07.924 - Client closed connection 15140:S 24 Jan 2025 11:06:07.924 - Client closed connection 15140:S 24 Jan 2025 11:06:07.983 - Accepted 192.168.51.163:53861 15140:S 24 Jan 2025 11:06:07.983 - Accepted 192.168.51.163:60301 15140:S 24 Jan 2025 11:06:31.018 - Accepted 192.168.51.160:39342 15140:S 24 Jan 2025 11:06:31.019 - Client closed connection 15140:S 24 Jan 2025 11:07:01.018 - Accepted 192.168.51.160:35312 15140:S 24 Jan 2025 11:07:01.021 - Client closed connection 15140:S 24 Jan 2025 11:07:31.018 - Accepted 192.168.51.160:56930 15140:S 24 Jan 2025 11:07:31.020 - Client closed connection 15140:S 24 Jan 2025 11:08:01.018 - Accepted 192.168.51.160:53092 15140:S 24 Jan 2025 11:08:01.020 - Client closed connection 15140:S 24 Jan 2025 11:08:31.019 - Accepted 192.168.51.160:53130 15140:S 24 Jan 2025 11:08:31.021 - Client closed connection 15140:S 24 Jan 2025 11:09:01.018 - Accepted 192.168.51.160:35752 15140:S 24 Jan 2025 11:09:01.019 - Client closed connection 15140:M 24 Jan 2025 11:09:04.322 # Connection with master lost. 15140:M 24 Jan 2025 11:09:04.322 * Caching the disconnected master state. 15140:S 24 Jan 2025 11:09:04.322 * Connecting to MASTER 192.168.51.161:6379 15140:S 24 Jan 2025 11:09:04.322 * MASTER <-> REPLICA sync started 15140:S 24 Jan 2025 11:09:04.322 * REPLICAOF 192.168.51.161:6379 enabled (user request from 'id=117 addr=192.168.51.165:47479 laddr=192.168.51.160:6379 fd=9 name=sentinel-fdbe92a7-cmd age=181 idle=0 flags=x db=0 sub=0 psub=0 multi=4 qbuf=202 qbuf-free=40752 argv-mem=4 obl=45 oll=0 omem=0 tot-mem=61468 events=r cmd=exec user=default redir=-1') 15140:S 24 Jan 2025 11:09:04.325 # CONFIG REWRITE executed with success. 15140:S 24 Jan 2025 11:09:04.326 * Non blocking connect for SYNC fired the event. 15140:S 24 Jan 2025 11:09:04.327 * Master replied to PING, replication can continue... 15140:S 24 Jan 2025 11:09:04.327 * Trying a partial resynchronization (request b593051fad65a8c04dd061a548bf955abacfd00f:746938). 15140:S 24 Jan 2025 11:09:04.327 * Successful partial resynchronization with master. 15140:S 24 Jan 2025 11:09:04.328 * MASTER <-> REPLICA sync: Master accepted a Partial Resynchronization. 15140:S 24 Jan 2025 11:09:04.347 - Accepted 192.168.51.163:42735 15140:S 24 Jan 2025 11:09:04.347 - Accepted 192.168.51.163:35633 15140:S 24 Jan 2025 11:09:04.363 - Accepted 192.168.51.175:51357 15140:S 24 Jan 2025 11:09:04.363 - Accepted 192.168.51.175:34647 15140:S 24 Jan 2025 11:09:04.366 - Accepted 192.168.51.177:47547 15140:S 24 Jan 2025 11:09:04.367 - Accepted 192.168.51.177:47289 15140:S 24 Jan 2025 11:09:04.379 - Accepted 192.168.51.176:34213 15140:S 24 Jan 2025 11:09:04.379 - Accepted 192.168.51.176:51139 15140:S 24 Jan 2025 11:09:04.393 - Accepted 192.168.51.165:44521 15140:S 24 Jan 2025 11:09:04.411 - Accepted 192.168.51.164:59481 15140:S 24 Jan 2025 11:09:04.411 - Accepted 192.168.51.164:36519 15140:S 24 Jan 2025 11:09:31.018 - Accepted 192.168.51.160:58046 15140:S 24 Jan 2025 11:09:31.022 - Client closed connection 15140:S 24 Jan 2025 11:10:01.019 - Accepted 192.168.51.160:42166 15140:S 24 Jan 2025 11:10:01.020 - Client closed connection 15140:S 24 Jan 2025 11:10:31.018 - Accepted 192.168.51.160:39956 15140:S 24 Jan 2025 11:10:31.019 - Client closed connection 15140:S 24 Jan 2025 11:11:01.019 - Accepted 192.168.51.160:36476 15140:S 24 Jan 2025 11:11:01.025 - Client closed connection 15140:S 24 Jan 2025 11:11:31.018 - Accepted 192.168.51.160:56160 15140:S 24 Jan 2025 11:11:31.022 - Client closed connection 15140:S 24 Jan 2025 11:12:01.018 - Accepted 192.168.51.160:46588 15140:S 24 Jan 2025 11:12:01.020 - Client closed connection 15140:S 24 Jan 2025 11:12:31.018 - Accepted 192.168.51.160:60684 15140:S 24 Jan 2025 11:12:31.020 - Client closed connection 15140:S 24 Jan 2025 11:13:01.019 - Accepted 192.168.51.160:52374 15140:S 24 Jan 2025 11:13:01.024 - Client closed connection 15140:S 24 Jan 2025 11:13:31.018 - Accepted 192.168.51.160:44758 15140:S 24 Jan 2025 11:13:31.020 - Client closed connection 15140:S 24 Jan 2025 11:14:01.018 - Accepted 192.168.51.160:45030 15140:S 24 Jan 2025 11:14:01.020 - Client closed connection 15140:S 24 Jan 2025 11:14:31.018 - Accepted 192.168.51.160:46932 15140:S 24 Jan 2025 11:14:31.019 - Client closed connection 15140:S 24 Jan 2025 11:15:01.019 - Accepted 192.168.51.160:55042 15140:S 24 Jan 2025 11:15:01.023 - Client closed connection 15140:S 24 Jan 2025 11:15:31.018 - Accepted 192.168.51.160:54812 15140:S 24 Jan 2025 11:15:31.020 - Client closed connection 15140:S 24 Jan 2025 11:16:01.018 - Accepted 192.168.51.160:36128 15140:S 24 Jan 2025 11:16:01.021 - Client closed connection 15140:S 24 Jan 2025 11:16:31.018 - Accepted 192.168.51.160:44742 15140:S 24 Jan 2025 11:16:31.020 - Client closed connection 15140:S 24 Jan 2025 11:17:01.018 - Accepted 192.168.51.160:53076 15140:S 24 Jan 2025 11:17:01.022 - Client closed connection 15140:S 24 Jan 2025 11:17:31.018 - Accepted 192.168.51.160:38060 15140:S 24 Jan 2025 11:17:31.019 - Client closed connection 15140:S 24 Jan 2025 11:18:01.018 - Accepted 192.168.51.160:59124 15140:S 24 Jan 2025 11:18:01.019 - Client closed connection 15140:S 24 Jan 2025 11:18:04.441 - Accepted 172.16.15.134:47052 15140:S 24 Jan 2025 11:18:04.490 - Client closed connection 15140:S 24 Jan 2025 11:18:09.634 - Accepted 172.16.15.134:56128 15140:S 24 Jan 2025 11:18:09.682 - Client closed connection 15140:S 24 Jan 2025 11:18:31.018 - Accepted 192.168.51.160:46878 15140:S 24 Jan 2025 11:18:31.020 - Client closed connection 15140:S 24 Jan 2025 11:19:01.019 - Accepted 192.168.51.160:46390 15140:S 24 Jan 2025 11:19:01.024 - Client closed connection 15140:S 24 Jan 2025 11:19:31.019 - Accepted 192.168.51.160:46394 15140:S 24 Jan 2025 11:19:31.021 - Client closed connection 15140:S 24 Jan 2025 11:20:01.018 - Accepted 192.168.51.160:36472 15140:S 24 Jan 2025 11:20:01.022 - Client closed connection 15140:S 24 Jan 2025 11:20:31.018 - Accepted 192.168.51.160:50536 15140:S 24 Jan 2025 11:20:31.024 - Client closed connection
Comment From: kamilcieslak5100
i switched form 01 to 04, and now master is 02, why? this is a problem with sentinel?
Comment From: sundb
@kamilcieslak5100 yes, when you failover 01 to 04, both of them are unavailable and sentinel may select new master in 02 and 03.
Comment From: kamilcieslak5100
So, how I should setup sentinel to avoid this situation?
Comment From: sundb
you can try the following:
1) incr the slave-priority of redis 04
2) use sentinel failover <redis01 name>
normally, the sentinel will choose the 04 as the new master.
Comment From: kamilcieslak5100
@sundb i will test it tommorow and will be back as soon as possible. Thanks for clarifications!