From 55e8d4cf1b1b23b329d69d82e94dac285d2bcb1c Mon Sep 17 00:00:00 2001 From: antirez Date: Mon, 29 Jun 2015 17:23:47 +0200 Subject: [PATCH] Add 3.0 changed config default for maxmemory policy to release notes. --- 00-RELEASENOTES | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/00-RELEASENOTES b/00-RELEASENOTES index c1cbed36..0f2e901c 100644 --- a/00-RELEASENOTES +++ b/00-RELEASENOTES @@ -608,6 +608,11 @@ non-backward compatible changes introduced in the 3.0 release: '?' is actually the role of the instance. M for master, S for slave, C if this process is a saving child (for RDB/AOF), and X for Sentinel. +* The default maxmemory policy in Redis 3.0 is no longer "volatile-lru" as + it used to be in 2.8, but "noeviction". The policies behavior is the same + (but LRU eviction is much more precise in 3.0), so only the default value + changed. Just make sure to specify in your redis.conf what you mean. + -------------------------------------------------------------------------------- Credits: Where not specified the implementation and design is done by