Bug 1314971 - Update to redis 3.0 in EPEL7
Update to redis 3.0 in EPEL7
Product: Fedora EPEL
Classification: Fedora
Component: redis (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Flavio Percoco
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-03-05 06:07 EST by pall.valmundsson
Modified: 2017-03-20 09:20 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-03-20 09:20:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description pall.valmundsson 2016-03-05 06:07:06 EST
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 [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.

- http://download.redis.io/redis-stable/00-RELEASENOTES
Comment 1 Tadej Janež 2017-03-20 09:20:53 EDT
Update to redis-3.2.3-1.el7 has been pushed to stable 6 days ago:

Note You need to log in before you can comment on or make changes to this bug.