Lines Matching refs:is
9 HIGH: There is a critical bug that may affect a subset of users. Upgrade!
10 CRITICAL: There is a critical bug affecting MOST USERS. Upgrade ASAP.
21 this is a minor release of Redis addressing two bugs:
24 a replication delay. This is not an actual problem since things work
28 reding from the file. This was actually a bug in linenoise which is
29 now fixed. The applied fix is from Chris Lamb.
48 Hi all! Redis 3.2.2 is finally out with non trivial bugfixes and a few new
53 when the LSET command was used. Now the bug is fixed and a new stress tester
60 This is not really a bug fix, but may allow to more easily detect that
61 a slave is able to fail over its master reducing certain delays.
64 process could spawn at the same time. This is known to trash disk I/O,
77 It's not a critical bug: the effect is to, sometimes, don't report objects
82 And now the good news (not that bug fixes are not good...), that is, the
91 2. The RDB check utlity is now part of Redis and uses the same RDB code that
93 of Redis is always able to check the RDB it produced... without another
94 external check tool which is supposed to be taken in sync with the
96 is able to spot more complex bugs, since it really loads the dataset
99 About the redis-check-dump utility, now it is also able to show certain
172 CONFIG GET is now no longer case sensitive.
212 A string with 21 chars is not representable as a 64-bit integer.
238 Hey, this is Redis 3.2.1, and this release should bring some grain of
250 when it is reachable again, as the slave of the new master. This was due
259 5. Jemalloc now is really configured to save you memory, for a problem a
270 8. TCP keep alive is now enabled by default. This should fix most ghost
306 which is a lot more complex than the 3.0 code, but more scalable.
324 the arguments, defaulting to instance 6379. After the connection is
327 The effect is that if there is an instance running on port 6339,
328 whatever port you specify is ignored and 6379 is connected to instead.
357 older versions of Redis, and the only places where it is needed the
358 current version in order to correctly restore data, is while loading the
394 separators as Redis code base normally does (camel case is mostly used
408 fixes #3259 and #3221, and also an early return if wrongtype is discovered by SET
532 computed (which is invalid) only then it was trimmed to 25 instead of
546 Probably there is no compiler that will actaully break the code or raise
672 | fix crash in BITFIELD GET when key is integer encoded
717 This change is documented in deps/README.md but was lost in one way or
734 exported by the Redis server it is connected to, but were not available
758 Hello, this is Redis 3.2.0 stable! And with the new release there is a new
759 format for the changelog. Now it is composed of a "letter" like the one
774 * There is a new very powerful BITFIELD command. Check the documentation
777 * CONFIG GET is allowed during the loading of the dataset.
790 cluster has a slave, then the new master is considered a valid target for
791 replica migration. So if it will be orphaned and there is a spare slave
800 As usually what "stable" means is that we are confident the release is mature,
835 Actually this is wrong, the command can be called without args at all.
874 | redis-cli: don't free historyfile, is used later.
900 with the logic of always allowing, while the cluster is down, commands
903 As a side effect the code is also simpler now.
925 Fix issue in case the redirect address is in ipv6 format. Parse from behind to extract last part of…
971 I've renamed maxmemoryToString to evictPolicyToString since that is
974 server.maxmemory. Now with a default config it is actually returning
1147 The test works but is very slow so far, since it involves resharding
1165 is no longer considered a target for migration, because the system has
1169 new rule. When a new or old master which is empty and without slaves,
1228 As a side effect, cat commands.txt | redis-cli now is able to handle
1265 The problem with the old implementation is that, the time returned by
1266 a timer event (that is the time after it want to run again) is added
1269 infinite loop is triggered.
1298 | BITFIELD: Farest bit set is offset+bits-1. Off by one error fixed.
1350 | Fix INFO commandstats reporting when argv is rewritten.
1356 even when what is actually executed is the ZADD implementation.
1398 The new bitfield command is an extension to the Redis bit operations,
1419 This commit is the resulting implementation.
1578 NODES, that is not a stable API and may change frequently depending on
1611 the specified weight is zero.
1623 * [FIX] Redis-trib is now able to fix more errors. A new CLUSTER subcommand
1627 harder to run Redis in a configuration that is unsecure because no
1639 This is the first release candidate of Redis 3.2. The changelog above shows
1673 the delay there is sometimes between the natural expire of the key
1674 and the moment the slave is notified. (Salvatore Sanfilippo)
1704 All the Redis Cluster changes in 3.2 were backported to 3.0, so there is
1709 * A pipelined MIGRATE command which is 10x faster and makes resharding
1713 lists between nodes is now a lot faster.
1725 Redis 3.0 is mostly a strict subset of 3.2, you should not have any problem
1726 upgrading your application from 3.0 to 3.2. However this is a list of small
1731 * The RDB format changed. Redis 3.2 is still able to read 3.0 (and all the
1734 the memory test executed is now different.
1738 Credits: For each release, a list of changes with the relative author is
1739 provided. Where not specified the implementation and design is done by