From b028b48b2b169fd294575eda84785cd350c372f4 Mon Sep 17 00:00:00 2001 From: Michael Chaten Date: Fri, 6 Dec 2019 11:56:52 -0800 Subject: [PATCH 1/2] Fix outdated information on max memory policies --- redis.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/redis.conf b/redis.conf index c4bf60222..27365641b 100644 --- a/redis.conf +++ b/redis.conf @@ -811,7 +811,7 @@ replica-priority 100 # maxmemory # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory -# is reached. You can select among five behaviors: +# is reached. You can select among eight behaviors: # # volatile-lru -> Evict using approximated LRU, only keys with an expire set. # allkeys-lru -> Evict any key using approximated LRU. From 71ec9478a63673af90c2ddc0d8fd06a5e4325ec5 Mon Sep 17 00:00:00 2001 From: Michael Chaten Date: Mon, 9 Dec 2019 11:27:53 -0800 Subject: [PATCH 2/2] Change description to be agnostic to the number of policies. --- redis.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/redis.conf b/redis.conf index 27365641b..d37760176 100644 --- a/redis.conf +++ b/redis.conf @@ -811,7 +811,7 @@ replica-priority 100 # maxmemory # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory -# is reached. You can select among eight behaviors: +# is reached. You can select one from the following behaviors: # # volatile-lru -> Evict using approximated LRU, only keys with an expire set. # allkeys-lru -> Evict any key using approximated LRU.