Add maxmemory slave behavior change in the change log.

This commit is contained in:
antirez 2018-08-29 12:31:52 +02:00
parent 5ad888ba17
commit 4cb9ee111e

View File

@ -1237,6 +1237,14 @@ non-backward compatible changes introduced in the 5.0 release:
* Certain log formats and sentences are different in Redis 5.0.
* Now by default maxmemory is ignored by slaves, and used only once a slave
is promoted to master. It means that in setups where you want slaves to
enforce maxmemory in an independent way from the master (that will anyway
stream the key eviction DEL commands), you should active this feature manually
and make sure you understand that it breaks consistency if writes are not
always idempotent. TLDR: the new behavior is much better for 99.999% of use
cases, revert it if you really know what you are doing.
--------------------------------------------------------------------------------
Credits: For each release, a list of changes with the relative author is