summaryrefslogtreecommitdiff
path: root/00-RELEASENOTES
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2018-09-05 19:58:25 +0200
committerantirez <antirez@gmail.com>2018-09-05 19:58:25 +0200
commit1d1bf7f032cd3d5d249c834b634fad91b4a8a4e6 (patch)
tree25a8870cc43c0c4d730b8ab06e4c41c0544eb819 /00-RELEASENOTES
parentcfd969c77710c1a937465a13b16b3a29e027e255 (diff)
downloadredis-1d1bf7f032cd3d5d249c834b634fad91b4a8a4e6.tar.gz
Document that effects replication is Redis 5 default.
Diffstat (limited to '00-RELEASENOTES')
-rw-r--r--00-RELEASENOTES8
1 files changed, 8 insertions, 0 deletions
diff --git a/00-RELEASENOTES b/00-RELEASENOTES
index 6e37a1cec..dad2049e4 100644
--- a/00-RELEASENOTES
+++ b/00-RELEASENOTES
@@ -1245,6 +1245,14 @@ non-backward compatible changes introduced in the 5.0 release:
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.
+* Scripts are only replicated by their *effects* and not by sending EVAL/EVALSHA
+ to slaves or the AOF log itself. This is much better in the general case
+ and in the future we want to totally remove the other possiblity of propagating
+ scripts the old way (as EVAL). However you can still turn this back to the
+ default via the non-documented (if not here) Redis configuration directive
+ "lua-replicate-commands yes" or "DEBUG lua-always-replicate-commands 0".
+ However note that Redis 6 may completely remove such feature.
+
--------------------------------------------------------------------------------
Credits: For each release, a list of changes with the relative author is