diff options
| author | Wen Hui <wen.hui.ware@gmail.com> | 2021-11-30 11:46:15 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-11-30 18:46:15 +0200 |
| commit | 2afa41f62847b92ba66f5579b4731494fac3afc3 (patch) | |
| tree | af2f348618efddd5b7a06ec5acfbd7070c92ed82 /sentinel.conf | |
| parent | af072c26bcf62dc4be1cfee7c2ca7242ac2d16aa (diff) | |
| download | redis-2afa41f62847b92ba66f5579b4731494fac3afc3.tar.gz | |
Sentinel master reboot fix (#9438)
Add master-reboot-down-after-period as a configurable parameter, to make it possible to trigger a failover from a master that is responding with `-LOADING` for a long time after being restarted.
Diffstat (limited to 'sentinel.conf')
| -rw-r--r-- | sentinel.conf | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/sentinel.conf b/sentinel.conf index c5341168e..b145ae518 100644 --- a/sentinel.conf +++ b/sentinel.conf @@ -339,3 +339,13 @@ SENTINEL resolve-hostnames no # to retain the hostnames when announced, enable announce-hostnames below. # SENTINEL announce-hostnames no + +# When master_reboot_down_after_period is set to 0, Sentinel does not fail over +# when receiving a -LOADING response from a master. This was the only supported +# behavior before version 7.0. +# +# Otherwise, Sentinel will use this value as the time (in ms) it is willing to +# accept a -LOADING response after a master has been rebooted, before failing +# over. + +SENTINEL master-reboot-down-after-period mymaster 0 |