<ChangeLog>
Upgrade urgency HIGH: many issues fixed, some may have an impact.
Hi all, Redis 5.0.7 fixes a number of bugs, none is very critical, however
there are a few that may have an impact. It's a good idea to upgrade.
There are fixes in the area of replication from modules commands and
callbacks, AOF fsync (non critical issue), memory leaks (very rare and small),
streams beahvior (non critical), and a potential crash in commands
processing multiple keys at the same time that is there for years, and happens
very rarely, but is not impossible to trigger.
</ChangeLog>
Regenerate the patches to make portlint(1) happier.
<ChangeLog>
Upgrade urgency CRITICAL: Only in case of exposed instances to untrusted users.
This Redis release, 5.0.6, is a bugfix and enhancement release. The most
important bugfix is a corruption related to the HyperLogLog. A malformed
HyperLogLog string could cause an invalid access to the memory. At a first
glance the vulnerability appears to be not exploitable but just a DoS. The
way to trigger the issue is complex, we'll not provide any information about
how to do that for the users safety.
Other significant changes in this release:
* New modules APIs merged from Redis unstable to Redis 5.
* Some memory optimization related to objects creation.
* Fixes to flushSlaveOutputBuffer() that make sure that SHUTDOWN will
transfer pending buffers to replicas.
</ChangeLog>
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
as a stand-in for "are we running on gcc".
In some cases we only need to specifically test for "are we on the ancient
base gcc", e.g, the usage of 'pragma'.
While here, in some cases turn off SSE functions more specifically based
on ARCH, and turn off -mtune=generic everywhere. These are part of a
larger work in progress; these commits are for ports that would have
been touched by the the powerpc-on-clang test regardless.
Approved by: portmgr (tier-2 blanket)
<ChangeLog>
Upgrade urgency CRITICAL: This release fixes an important AOF fysnc bug
and other less critical issues.
Redis 5.0.5 fixes an important issue with AOF and adds multiple very useful
modules APIs. Moreover smaller bugs in other parts of Redis are fixed in
this release.
The AOF bug
-----------
The AOF bug happens when the fsync policy is set to "everysec", which is the
default: if the write load in the server drops immediately, the commands
executed in the latest second may not be fsync-ed to disk as it should.
This may lead to data loss in case the write load drops immediately and
successively a server crash happens.
Other things in this release
----------------------------
* Streams: a bug in the iterator could prevent certain items to be returned in
range queries under specific conditions.
* Memleak in bitfieldCommand fixed.
* Modules API: Preserve client->id for blocked clients.
* Fix memory leak when rewriting config file in case of write errors.
* New modules API: RedisModule_GetKeyNameFromIO().
* Fix non critical bugs in diskless replication.
* New mdouels API: command filtering. See RedisModule_RegisterCommandFilter();
* Tests improved to be more deterministic.
* Fix a Redis Cluster bug, manual failover may abort because of the master
sending PINGs to the replicas.
</ChangeLog>
M Makefile
M distinfo
<ChangeLog>
Upgrade urgency HIGH: This release fixes several Redis stability issues.
Dear Redis users, this release includes a number of fixes for bugs that may
result in Redis crashing in special conditions (not normal usage, but specific
artificial conditions), fixes to certain Redis behaviors especially around
Redis streams, and finally a set of new APIs for Redis Modules.
Specifically:
* Hyperloglog different coding errors leading to potential crashes were fixed.
* A replication bug leading to a potential crash in case of plain misuse of
handshake commands was fixed.
* XCLAIM command incrementing of number of deliveries was fixed.
* LFU field management in objects was improved.
* A potential overflow in the redis-check-aof was fixed.
* A memory leak in case of API misuse was fixed.
* ZPOP* behavior when count is 0 is fixed.
* A few redis-cli --cluster bugs were fixed, plus a few improvements.
* Many other smaller bugs.
We suggest to upgrade Redis, especially in case your instance is facing
untrusted users (for instance Cloud providers) because several of these
bugs could result in unwanted crashes.
</ChangeLog>
<ChangeLog>
Upgrade urgency HIGH: Redis 5 is consolidating, upgrading is a good idea.
However there is nothing very critical here, but certain
issues resolved could lead to very rare crashes.
Welcome to Redis 5.0.3, several interesting bug fixes here:
* Redis no longer panics when you send data to a replica-mode connection that
is in MONITOR or SYNC mode.
* Fixes to certain sorted set edge cases. You are unlikely to ever notice those
issues, but now it is more correct.
* Certain BSD variants now are better supported: build & register logging
on crash.
* The networking core now recovers if an IPv6 address is listed in bind but
is actually not able to work because there is no such protocol in the
system.
* redis-cli cluster mode improved in many ways. Especially the fix subcommand
work was enhanced to cover other edge cases that were still not covered
after the work done for Redis 5.
* MEMORY USAGE is now more accurate.
* DEBUG DIGEST-VALUE added in case you want to make sure a given set of keys
(and not the whole DB) are excatly the same between two instances.
* Fix a potential crash in the networking code related to recent changes
to the way the reply is consumed.
* Reject EXEC containing write commands against an instance that changed role
from master to replica during our transaction.
* Fix a crash in KEYS and other commands using pattern matching, in an edge
case where the pattern contains a zero byte.
* Fix eviction during AOF loading due to maxmemory triggered by commands
executed in loading state.
</ChangeLog>
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
<ChangeLog>
Upgrade urgency: CRITICAL if you use streams and consumer groups.
HIGH if you use redis-cli with Redis Cluster.
LOW otherwise.
Welcome to Redis 5.0.2. This release fixes two issues with Streams consumer
groups, where items could be returned duplicated by XREADGROUP when accessing
the history, and another bug where XREADGROUP can report some history even
if the comsumer pending list is empty. Both problems were addressed and unit
tests to avoid regressions implemented. Moreover this release fixes some
issue with redis-cli when in cluster mode. Finally some FreeBSD and DragonFly
build problems are now resolved.
</ChangeLog>
<ChangeLog>
Upgrade urgency: URGENT if you use Redis Streams. MODERATE otherwise.
Hi all, this is the first patch level release of Redis 5. It contains
both fixes and improvements. Here there is a list of the major ones, however
read the commit messages at the end of the changelog if you want to know
more about the smaller things. Let's start with the new features:
* Sentinel now supports authentication! Check the Sentinel official doc
for more info.
* Redis-cli cluster "fix" is now able to fix a big number of clusters put
in a bad condition. Previously many corner cases were not covered.
Now the critical fixes:
1. Fix RESTORE mismatch reply when certain keys already expired.
2. Fix an XCLAIM non trivial issue: sometimes the command returned a wrong
entry or desynchronized the protocol.
And now the other fixes:
3. Stack trace generation on the Raspberry PI (and 32bit ARM) fixed.
4. Don't evict expired keys when the KEYS command is called, in order to
avoid a mass deletion event. However expired keys are not displayed
by KEYS as usually.
5. Improvements in the computation of the memory used, when estimating
the AOF buffers.
6. XRANGE COUNT of 0 fixed.
7. "key misses" stats accounting fixed. Many cache misses were not counted.
8. When in MULTI state, return OOM while accumulating commands and there
is no longer memory available.
9. Fix build on FreeBSD and possibly others.
10. Fix a crash in Redis modules, thread safe context reply accumulation.
11. Fix a race condition when producing the RDB file for full SYNC.
12. Disable protected mode in Sentinel.
13. More commands now have the HELP subcommand.
14. Fixed an issue about adaptive server HZ timer.
15. Fix cluster-replica-no-failover option name.
</ChangeLog>
<ChangeLog>
Upgrade urgency CRITICAL: Several fixes to streams AOF and replication.
Hi all and welcome to the first stable release of Redis 5! \o/
To start a quick recap of what's new in Redis 5:
1. The new Stream data type. https://redis.io/topics/streams-intro
2. New Redis modules APIs: Timers, Cluster and Dictionary APIs.
3. RDB now store LFU and LRU information.
4. The cluster manager was ported from Ruby (redis-trib.rb) to C code
inside redis-cli. Check `redis-cli --cluster help` for more info.
5. New sorted set commands: ZPOPMIN/MAX and blocking variants.
6. Active defragmentation version 2.
7. Improvemenets in HyperLogLog implementations.
8. Better memory reporting capabilities.
9. Many commands with sub-commands now have an HELP subcommand.
10. Better performances when clients connect and disconnect often.
11. Many bug fixes and other random improvements.
12. Jemalloc was upgraded to version 5.1
13. CLIENT UNBLOCK and CLIENT ID.
14. The LOLWUT command was added. http://antirez.com/news/123
15. We no longer use the "slave" word if not for API backward compatibility.
16. Differnet optimizations in the networking layer.
17. Lua improvements:
- Better propagation of Lua scripts to slaves / AOF.
- Lua scripts can now timeout and get in -BUSY state in the slave as well.
18. Dynamic HZ to balance idle CPU usage with responsiveness.
19. The Redis core was refactored and improved in many ways.
</ChangeLog>
<ChangeLog>
Upgrade urgency HIGH: Several imporant bugs fixed.
This is the release candidate number five, and has a lot of bug fixes inside,
together with a few big changes to the Redis behavior from the point of view
of replication of scripts and handling of the maxmemory directive in slaves.
Make sure to read the whole list!
* BREAKING BEHAVIOR: Slaves now ignore maxmemory by default.
* BREAKING BEHAVIOR: Now scripts are always replicated for their effects, and
never sending the script itself to slaves/AOF.
* Improvement: Big pipelining performances improved significantly.
* Fix: Rewrite BRPOPLPUSH as RPOPLPUSH to propagate.
* Fix: False positives in tests.
* Fix: Certain command flags were modified because not correct.
* Fix: Fix blocking XREAD for streams that are empty.
* Improvement: Allow scripts to timeout on slaves as well.
* Fix: Different corner cases due to CLIENT PAUSE are now fixed.
* Improvement: Optimize parsing large bulk greater than 32k.
* Fix: Propagate read-only scripts as SCRIPT LOAD, not as EVAL.
</ChangeLog>
<ChangeLog>
Upgrade urgency
HIGH: Many non critical but important issues fixed.
CRITICAL for Stream users: Many important bugs fixed.
Fixes:
* A number of fixes related to Streams: stability and correctnes.
* Fix dbRandomKey() potential infinite loop.
* Improve eviction LFU/LRU when keys are created by INCR commands family.
* Active defragmentation is now working on Redis 5.
* Fix corner case in Redis CLuster / Sentinel failover, by resetting the
disconnection time with master in a more appropriate place.
* Use a private version of localtime() to avoid potential deadlocks.
* Different redis-cli non critical fixes.
* Fix rare replication stream corruption with disk-based replication.
Improvements:
* Sentinel: add an option to deny online script reconfiguration.
* Improved RESTORE command.
* Sentinel command renaming: allows to use Sentinel with Redis instances
that have non standard command names.
* CLIENT ID and CLIENT UNBLOCK.
* CLIENT LIST now supports a TYPE option.
* redis-cli --cluster now supports authentication.
* redis-trib is now deprecated (use redis-cli --cluster).
* Better slaves output buffers efficiency.
* Faster INFO when there are many clients connected.
* Dynamic HZ feature.
* Improvements in what the MEMORY command is able to report.
* Add year in log. (WARNING: may be incompatible with log scraping tools)
* Lazy freeing now works even when values are overwritten (for instance SET).
* Faster ZADD when elements scores are updated.
* Improvements to the test suite, including many new options.
</ChangeLog>
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
<ChangeLog>
Upgrade urgency CRITICAL ONLY for Redis Cluster users. Otherwise no reason
to upgrade at all.
Redis 4.0.8 fixes a single critical bug in the radix tree data structure
used for Redis Cluster keys slot tracking. The problem was actually fixed
10 months ago into unstable, but it was fixed in a commit related to Streams
so it was never backported (for error) into the 4.0 branch.
The problem will crash Redis Cluster instances during deletions, but it is
very hard to trigger: only when the node removed is in the edge of a memory
mapped area there are the conditions to create an issue, because otherwise
the code just accesses an out of range word in read-only way in an allocated
structure: this is almost always harmless.
</ChangeLog>
<ChangeLog>
* Many 32 bit overflows were addressed in order to allow to use Redis with
a very significant amount of data, memory size permitting. (zhaozhao.zz,
Oran Agra)
* MEMORY USAGE fixed for the list type. (gnuhpc)
* Allow read-only scripts in Redis Cluster. (Salvatore Sanfilippo)
* Fix AOF pipes setup in edge case. (heqin)
* AUTH option for MIGRATE. (AlexStocks, Salvatore Sanfilippo, Fabio Nicotra)
* HyperLogLogs are no longer converted from sparse to dense in order
to be merged. (Salvatore Sanfilippo)
* Fix AOF rewrite dead loop under edge cases. (heqin)
* Fix processing of large bulk strings (>= 2GB). (Oran Agra)
* Added RM_UnlinkKey in modules API. (Dvir Volk)
* Fix Redis Cluster crashes when certain commands with a variable number
of arguments are called in an improper way. (Salvatore Sanfilippo)
* Fix memory leak in lazyfree engine. (zhaozhao.zz)
* Fix many potentially successful partial synchronizations that end
doing a full SYNC, because of a bug destroying the replication
backlog on the slave. So after a failover the slave was often not able
to PSYNC with masters, and a full SYNC was triggered. The bug only
happened after 1 hour of uptime so escaped the unit tests. (Oran Agra)
* Improve anti-affinity in master/slave allocation for Redis Cluster
when the cluster is created. (Salvatore Sanfilippo)
* Improve output buffer handling for slaves, by not limiting the amount
of writes a slave could receive. (Guy Benoish)
</ChangeLog>
networking.o: In function `createClient':
networking.c:(.text+0x189): undefined reference to `__atomic_fetch_add_8'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
Sponsored by: Absolight
networking.o: In function `createClient':
networking.c:(.text+0x189): undefined reference to `__atomic_fetch_add_8'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
Do not bump PORTREVISION since this change affects i386 only what's broken till now.
networking.o: In function `createClient':
networking.c:(.text+0x189): undefined reference to `__atomic_fetch_add_8'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
Sponsored by: Absolight
<ChangeLog>
Upgrade urgency LOW: This release mainly fixes a rare GEO API bug and a crash
related to the modules subsystem.
Redis 4.0.0-RC2 (version number 3.9.102) just fixes two bugs:
1. GEORADIUS could fail reporting items with very big radius lengths because
of a bug in the bounding box computation function. This was fixed and tests
with large radius sizes were added.
2. There was a crash in the modules subsystem that was not merged into RC1 for
an error, while it was already fixed into the "unstable" branch.
</ChangeLog>
<ChangeLog>
Upgrade urgency LOW: This release only fixes a compilation issue due to the
missing -ldl at linking time.
zach shipko in commit 4736407:
BSDs don't have -ldl
1 file changed, 15 insertions(+), 5 deletions(-)
antirez in commit 9ada818:
Fix modules compilation when libc malloc is used.
1 file changed, 2 insertions(+), 2 deletions(-)
</ChangeLog>
