From 461a13ffc6c0c0bc77b2ddf475fe19c101e2fd15 Mon Sep 17 00:00:00 2001 From: Binbin Date: Sat, 21 Sep 2024 21:09:13 +0800 Subject: [PATCH] Fix default value of primary-reboot-down-after-period in sentinel.conf (#1040) Since in here the monitor value is mymaster, we need to make sure the primary name is the same, otherwise the default configuration cannot start sentinel. ``` sentinel monitor mymaster 127.0.0.1 6379 2 ``` The following error occurs when the default configuration is started: ``` *** FATAL CONFIG FILE ERROR (Version 255.255.255) *** Reading the configuration file, at line 358 >>> 'SENTINEL primary-reboot-down-after-period myprimary 0' No such master with specified name. ``` Introduced in #647. Signed-off-by: Binbin --- sentinel.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sentinel.conf b/sentinel.conf index dcdd7d3d01..4c98a090ab 100644 --- a/sentinel.conf +++ b/sentinel.conf @@ -355,4 +355,4 @@ SENTINEL announce-hostnames no # accept a -LOADING response after a primary has been rebooted, before failing # over. -SENTINEL primary-reboot-down-after-period myprimary 0 +SENTINEL primary-reboot-down-after-period mymaster 0