Red Hat Bugzilla – Bug 1314971
Update to redis 3.0 in EPEL7
Last modified: 2017-03-20 09:20:53 EDT
Requesting an update to redis 3.0 for EPEL7.
The "non-backward compatible changes" look like they should only cause very minor issues, if any.
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 . 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.
Update to redis-3.2.3-1.el7 has been pushed to stable 6 days ago: