Redis failover-timeout removed from conf file after restart sentinel service

Describe the bug

Some options removed removed after restart sentinel service

To reproduce

Add some options to sentinel.conf file

daemonize no
acllog-max-len 128
sentinel parallel-syncs redishost_master 1 # added
sentinel failover-timeout redishost_master 180000 # added
sentinel master-reboot-down-after-period redishost_master 0 # added

# Generated by CONFIG REWRITE
dir "/tmp"
supervised systemd
protected-mode no
port 26379
latency-tracking-info-percentiles 50 99 99.9
pidfile "/run/redis/redis-sentinel-26379.pid"
logfile "/var/log/redis/redis-sentinel-redishost.log"
user default on nopass sanitize-payload ~* &* +@all
sentinel myid ...
sentinel resolve-hostnames yes
sentinel announce-hostnames yes
sentinel monitor redishost_master redis-host.somenet.com 6379 2
sentinel down-after-milliseconds redishost_master 5000
sentinel config-epoch redishost_master 0
sentinel leader-epoch redishost_master 0
sentinel current-epoch 0
sentinel announce-ip "redis-host2.somenet.com"

sentinel known-replica ...
sentinel known-sentinel ...
sentinel known-sentinel ...

Then restart sentinel service. Bug: Following options do not exist in sentinel.conf anymore:

sentinel parallel-syncs
sentinel failover-timeout
sentinel master-reboot-down-after-period

Other options untouched.

Expected behavior

Only options after # Generated by CONFIG REWRITE may be changed

Additional information

Redis version: redis-stack-server 7.0.6-RC5

Comment From: hwware

Let me check it. Please wait one or two days, Thanks

Comment From: hwware

The behavior is correct becuase in your config file, the values of the parameters parallel-syncs, failover-timeout and master-reboot-down-after-period are default. Default values are not rewritten in sentinel config file. If you change these parameters to other values, they will not be removed from config file.

Thanks

Comment From: damanis

@hwware Accept. Thank you.