From bb30b9f913ced7380cd4a46451cdebf3588f337d Mon Sep 17 00:00:00 2001 From: antirez Date: Mon, 6 Apr 2020 17:32:04 +0200 Subject: Clarify redis.conf comment about lazyfree-lazy-user-del. --- redis.conf | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/redis.conf b/redis.conf index 14388e320..5baeae65f 100644 --- a/redis.conf +++ b/redis.conf @@ -936,23 +936,27 @@ replica-priority 100 # or SORT with STORE option may delete existing keys. The SET command # itself removes any old content of the specified key in order to replace # it with the specified string. -# 4) The DEL command itself, and normally it's not easy to replace DEL with -# UNLINK in user's codes. -# 5) During replication, when a replica performs a full resynchronization with +# 4) During replication, when a replica performs a full resynchronization with # its master, the content of the whole database is removed in order to # load the RDB file just transferred. # # In all the above cases the default is to delete objects in a blocking way, # like if DEL was called. However you can configure each case specifically # in order to instead release memory in a non-blocking way like if UNLINK -# was called, using the following configuration directives: +# was called, using the following configuration directives. lazyfree-lazy-eviction no lazyfree-lazy-expire no lazyfree-lazy-server-del no -lazyfree-lazy-user-del no replica-lazy-flush no +# It is also possible, for the case when to replace the user code DEL calls +# with UNLINK calls is not easy, to modify the default behavior of the DEL +# command to act exactly like UNLINK, using the following configuration +# directive: + +lazyfree-lazy-user-del no + ################################ THREADED I/O ################################# # Redis is mostly single threaded, however there are certain threaded -- cgit v1.2.1