redis-sentinel出现了2个master

[shenkonghui]

reids-0 原来的slave，执行failover后成为master

10.244.37.170:6379> info Replication
# Replication
role:master
connected_slaves:0
master_failover_state:no-failover
master_replid:36562ad87a7617e0ea16a507fed663829d499e10
master_replid2:754e370b31f7f4ddf67d0bc753bbff27df6dd8ba
master_repl_offset:13324916
second_repl_offset:13239532
repl_backlog_active:1
repl_backlog_size:268435456
repl_backlog_first_byte_offset:12075877
repl_backlog_histlen:1249040

reids-1 原来的master，执行failover后还是master

10.244.185.149:6379>
# Replication
role:master
connected_slaves:0
master_failover_state:no-failover
master_replid:754e370b31f7f4ddf67d0bc753bbff27df6dd8ba
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:13330024
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:268435456
repl_backlog_first_byte_offset:1
repl_backlog_histlen:13330024

Sentinel 均是指向新的master

127.0.0.1:26379> 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=mymaster0,status=ok,address=10.244.37.170:6379,slaves=1,sentinels=3

[shenkonghui]

日志如下

Sentinel

1:X 18 May 2023 03:02:18.438 # Executing user requested FAILOVER of 'mymaster0'
1:X 18 May 2023 03:02:18.438 # +new-epoch 671
1:X 18 May 2023 03:02:18.438 # +try-failover master mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:18.475 # +vote-for-leader b9653acdea363a94879ddb034ac2960738dedc07 671
1:X 18 May 2023 03:02:18.475 # +elected-leader master mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:18.475 # +failover-state-select-slave master mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:18.543 # +selected-slave slave 10.244.37.170:6379 10.244.37.170 6379 @ mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:18.543 * +failover-state-send-slaveof-noone slave 10.244.37.170:6379 10.244.37.170 6379 @ mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:18.621 * +failover-state-wait-promotion slave 10.244.37.170:6379 10.244.37.170 6379 @ mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:19.612 # +promoted-slave slave 10.244.37.170:6379 10.244.37.170 6379 @ mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:19.612 # +failover-state-reconf-slaves master mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:19.688 # +failover-end master mymaster0 10.244.185.149 6379
1:X 18 May 2023 03:02:19.688 # +switch-master mymaster0 10.244.185.149 6379 10.244.37.170 6379
1:X 18 May 2023 03:02:19.689 * +slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:02:29.814 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:02:39.855 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:02:49.888 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:02:59.908 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:03:09.975 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:03:19.979 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:03:30.022 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:03:40.028 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:03:50.039 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:04:00.061 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:04:10.076 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:04:20.117 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:04:30.185 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379
1:X 18 May 2023 03:04:40.221 * +convert-to-slave slave 10.244.185.149:6379 10.244.185.149 6379 @ mymaster0 10.244.37.170 6379

reids-0

1:S 18 May 2023 11:00:58.123 * 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.
1:S 18 May 2023 11:00:58.189 * Connecting to MASTER 10.244.185.149:6379
1:S 18 May 2023 11:00:58.290 * MASTER <-> REPLICA sync started
1:S 18 May 2023 11:00:58.338 * REPLICAOF 10.244.185.149:6379 enabled (user request from 'id=48406 addr=10.244.37.170:59056 laddr=10.244.37.170:6379 fd=13 name= age=669 idle=1 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=48 qbuf-free=40906 argv-mem=25 obl=0 oll=0 omem=0 tot-mem=61489 events=r cmd=slaveof user=default redir=-1')
1:S 18 May 2023 11:00:58.405 * Non blocking connect for SYNC fired the event.
1:S 18 May 2023 11:00:58.445 * Master replied to PING, replication can continue...
1:S 18 May 2023 11:00:58.542 * Trying a partial resynchronization (request 36562ad87a7617e0ea16a507fed663829d499e10:13390665).
1:S 18 May 2023 11:00:58.791 * Full resync from master: 754e370b31f7f4ddf67d0bc753bbff27df6dd8ba:13387709
1:S 18 May 2023 11:00:58.813 * Discarding previously cached master state.
1:S 18 May 2023 11:00:59.029 * MASTER <-> REPLICA sync: receiving 178 bytes from master to disk
1:S 18 May 2023 11:00:59.057 * MASTER <-> REPLICA sync: Flushing old data
1:S 18 May 2023 11:00:59.135 * MASTER <-> REPLICA sync: Loading DB in memory
1:S 18 May 2023 11:00:59.228 * Loading RDB produced by version 6.2.6
1:S 18 May 2023 11:00:59.306 * RDB age 6 seconds
1:S 18 May 2023 11:00:59.340 * RDB memory usage when created 257.51 Mb
1:S 18 May 2023 11:00:59.375 # Done loading RDB, keys loaded: 0, keys expired: 0.
1:S 18 May 2023 11:00:59.411 * MASTER <-> REPLICA sync: Finished with success
1:S 18 May 2023 11:00:59.453 * Background append only file rewriting started by pid 181600
1:S 18 May 2023 11:00:59.549 * AOF rewrite child asks to stop sending diffs.
181600:C 18 May 2023 11:00:59.629 * Parent agreed to stop sending diffs. Finalizing AOF...
181600:C 18 May 2023 11:00:59.647 * Concatenating 0.00 MB of AOF diff received from parent.
181600:C 18 May 2023 11:00:59.686 * SYNC append only file rewrite performed
181600:C 18 May 2023 11:00:59.710 * AOF rewrite: 0 MB of memory used by copy-on-write
1:S 18 May 2023 11:00:59.846 * Background AOF rewrite terminated with success
1:S 18 May 2023 11:00:59.883 * Residual parent diff successfully flushed to the rewritten AOF (0.00 MB)
1:S 18 May 2023 11:00:59.954 * Background AOF rewrite finished successfully
1:M 18 May 2023 11:02:23.598 # Connection with master lost.
1:M 18 May 2023 11:02:23.754 * Caching the disconnected master state.
1:M 18 May 2023 11:02:23.877 * Discarding previously cached master state.
1:M 18 May 2023 11:02:23.925 # Setting secondary replication ID to 754e370b31f7f4ddf67d0bc753bbff27df6dd8ba, valid up to offset: 13406600. New replication ID is 696eca02f02d57eed853d99332fb7cdb3af08ca5
1:M 18 May 2023 11:02:23.955 * MASTER MODE enabled (user request from 'id=48602 addr=10.244.185.186:35336 laddr=10.244.37.170:6379 fd=11 name=sentinel-b9653acd-cmd age=115 idle=0 flags=x db=0 sub=0 psub=0 multi=4 qbuf=188 qbuf-free=40766 argv-mem=4 obl=45 oll=0 omem=0 tot-mem=61468 events=r cmd=exec user=default redir=-1')
1:M 18 May 2023 11:02:24.171 # CONFIG REWRITE executed with success.

reids-1

1:M 18 May 2023 11:02:18.924 # Connection with replica 10.244.37.170:6379 lost.