diff options
| author | antirez <antirez@gmail.com> | 2018-09-17 15:29:01 +0200 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2018-09-17 15:29:04 +0200 |
| commit | 378218d746b04039827f53a2e92e32f19be02ca6 (patch) | |
| tree | faa6528eed8793d6095792018d64ca87ffa090d1 /sentinel.conf | |
| parent | c560ade831ad6196d51cd42fd533ed3664837e54 (diff) | |
| download | redis-378218d746b04039827f53a2e92e32f19be02ca6.tar.gz | |
Sentinel: document how to undo a renamed command.
Diffstat (limited to 'sentinel.conf')
| -rw-r--r-- | sentinel.conf | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/sentinel.conf b/sentinel.conf index e428ad933..bc9a705ac 100644 --- a/sentinel.conf +++ b/sentinel.conf @@ -230,10 +230,15 @@ sentinel deny-scripts-reconfig yes # instead of the normal ones. For example if the master "mymaster", and the # associated replicas, have "CONFIG" all renamed to "GUESSME", I could use: # -# sentinel rename-command mymaster CONFIG GUESSME +# SENTINEL rename-command mymaster CONFIG GUESSME # # After such configuration is set, every time Sentinel would use CONFIG it will # use GUESSME instead. Note that there is no actual need to respect the command # case, so writing "config guessme" is the same in the example above. # # SENTINEL SET can also be used in order to perform this configuration at runtime. +# +# In order to set a command back to its original name (undo the renaming), it +# is possible to just rename a command to itsef: +# +# SENTINEL rename-command mymaster CONFIG CONFIG |