After the sentinel sent the slave no one，the new master without return info until the end of failover timeout。
43374:X 14 Jul 16:08:48.702 # +new-epoch 2
43374:X 14 Jul 16:08:48.702 # +try-failover master masterDAP1 158.220.153.212 6301
43374:X 14 Jul 16:08:48.706 # +vote-for-leader bf8e3dcb806b4a5e4792e18f99d6dfa0df557f9a 2
43374:X 14 Jul 16:08:48.719 # 158.220.153.212:26379 voted for bf8e3dcb806b4a5e4792e18f99d6dfa0df557f9a 2
43374:X 14 Jul 16:08:48.767 # 158.220.153.213:26379 voted for bf8e3dcb806b4a5e4792e18f99d6dfa0df557f9a 2
43374:X 14 Jul 16:08:48.777 # +elected-leader master masterDAP1 158.220.153.212 6301
43374:X 14 Jul 16:08:48.777 # +failover-state-select-slave master masterDAP1 158.220.153.212 6301
43374:X 14 Jul 16:08:48.830 # +selected-slave slave 158.220.153.213:6302 158.220.153.213 6302 @ masterDAP1 158.220.153.212 6301
43374:X 14 Jul 16:08:48.830 * +failover-state-send-slaveof-noone slave 158.220.153.213:6302 158.220.153.213 6302 @ masterDAP1 158.220.153.212 6301
43374:X 14 Jul 16:08:48.882 * +failover-state-wait-promotion slave 158.220.153.213:6302 158.220.153.213 6302 @ masterDAP1 158.220.153.212 6301
43374:X 14 Jul 16:11:48.895 # -failover-abort-slave-timeout master masterDAP1 158.220.153.212 6301
Comment From: hwware
Hello @heepy , it looks like some reason the promoted slave did not promote itself into master, may I ask you can you also attach the corresponding slave log and configurations? thanks
Comment From: heepy
Hello @heepy , it looks like some reason the promoted slave did not promote itself into master, may I ask you can you also attach the corresponding slave log and configurations? thanks
Thanks for your reply。The promoted slave has been promoted to new master。The slave log has show “CONFIG REWIRTE OK”。I see that no information to exchange when listened this channel--sentinel:hello.So,it looks like some reason the channel was destroyed。