Fixed active-expire-effort description in conf file (#1773)

Expired keys search happens without user actions. Therefore, the
"interactively" word in the description of the active-expire-key
parameter is confusing and is changed to "incrementally."
 
modified:   valkey.conf

---------

Signed-off-by: Anastasia Alexadrova <anastasia.alexandrova@percona.com>
This commit is contained in:
Anastasia Alexandrova 2025-02-25 11:06:27 +01:00 committed by GitHub
parent 0ca3974d3a
commit ee8465ce3b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions

View File

@ -1320,8 +1320,8 @@ acllog-max-len 128
# replica-ignore-maxmemory yes
# The server reclaims expired keys in two ways: upon access when those keys are
# found to be expired, and also in background, in what is called the
# "active expire key". The key space is slowly and interactively scanned
# found to be expired, and also in the background, in what is called the
# "active expire key". The key space is slowly and incrementally scanned
# looking for expired keys to reclaim, so that it is possible to free memory
# of keys that are expired and will never be accessed again in a short time.
#