redis - Redis v3.2.x 是否向后兼容 v2.8.x？

Question

我正在尝试从 Redis 2.8 升级到 3.2。我的应用程序中的所有功能似乎都完好无损，但我想知道

• 如果我需要处理一组非向后兼容的更改？
• 如果我在 Redis 2.8 中生成并持久保存到磁盘的数据将在 3.2 服务器上正常工作？

Answer 1

发行说明在 github 上 https://github.com/antirez/redis

这是 v3.0 和 v.3.2 发行说明中的​​一个片段

Migrating from 2.8 to 3.0 =========================

Redis 2.8 is mostly a strict subset of 3.0, you should not have any problem upgrading your application from 2.8 to 3.0. However this is a list of small non-backward compatible changes introduced in the 3.0 release:

• The log format was modified. The prefix of each line included the pid in the following format [1234]. Now instead it is 1234:? Where '?' 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.

https://raw.githubusercontent.com/antirez/redis/3.0/00-RELEASENOTES

Migrating from 3.0 to 3.2

Redis 3.0 is mostly a strict subset of 3.2, you should not have any problem upgrading your application from 3.0 to 3.2. However this is a list of small non-backward compatible changes introduced in the 3.2 release:

• The default configuration file now binds to 127.0.0.1.
• Slaves try to no longer expose stale data about already expired keys.
• The RDB format changed. Redis 3.2 is still able to read 3.0 (and all the past versions) files, but not the other way around.
• Behavior on crash may be different. The crash log format changed and the memory test executed is now different.

https://raw.githubusercontent.com/antirez/redis/3.2/00-RELEASENOTES