diff options
| author | antirez <antirez@gmail.com> | 2020-03-04 17:58:05 +0100 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2020-03-04 17:58:05 +0100 |
| commit | 4983eb6a23032d0e7e0b06a218ba5a2aa818714f (patch) | |
| tree | d029cda1b1d94e58062ef0ef7a2e0090c409cfff | |
| parent | 3bab69e921039ad2e4f56c5842c4cf3e73a598dd (diff) | |
| download | redis-nordb.tar.gz | |
RDB deletion: document it in example redis.conf.nordb
| -rw-r--r-- | redis.conf | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/redis.conf b/redis.conf index c04880f32..8609a9f57 100644 --- a/redis.conf +++ b/redis.conf @@ -321,6 +321,19 @@ rdbchecksum yes # The filename where to dump the DB dbfilename dump.rdb +# Remove RDB files used by replication in instances without persistence +# enabled. By default this option is disabled, however there are environments +# where for regulations or other security concerns, RDB files persisted on +# disk by masters in order to feed replicas, or stored on disk by replicas +# in order to load them for the initial synchronization, should be deleted +# ASAP. Note that this option ONLY WORKS in instances that have both AOF +# and RDB persistence disabled, otherwise is completely ignored. +# +# An alternative (and sometimes better) way to obtain the same effect is +# to use diskless replication on both master and replicas instances. However +# in the case of replicas, diskless is not always an option. +rdb-del-sync-files no + # The working directory. # # The DB will be written inside this directory, with the filename specified |