Lines Matching refs:in
23 1. There was an inverted if statement logic problem in replication.c causing
28 reding from the file. This was actually a bug in linenoise which is
33 Qu Chen in commit e67ad1d:
34 Fix a bug to delay bgsave while AOF rewrite in progress for replication
37 antirez in commit 7153668:
46 GEORADIUS errors in reported entries are fixed.
51 1. There was a bug in the List type implementation, able to cause the
65 AOF performances, and to ultimately create latency in the Redis server.
71 bad latency experiences in certain cases.
75 in the points reported by GEORADIUS. The errors were found to be related
76 to three different bugs (one of these was a bug in the test itself).
92 Redis uses in order to load the dataset in memory, so a given version
94 external check tool which is supposed to be taken in sync with the
95 rdb.c implementation. This in turn also means that the new RDB checking
114 modified in order to be a bit less verbose compared to the last releases.
119 antirez in commit 0a45fbc:
123 antirez in commit c3982c0:
127 antirez in commit fdafe23:
131 antirez in commit a1bfe22:
135 antirez in commit 7ca69af:
139 antirez in commit 5b5e652:
143 antirez in commit 21cffc2:
147 antirez in commit 017378e:
148 Replication: start BGSAVE for replication always in replicationCron().
151 antirez in commit 940be9a:
155 antirez in commit 21736b4:
159 antirez in commit 0b748e9:
160 redis-cli: check SELECT reply type just in state updated.
163 sskorgal in commit 1158386:
167 antirez in commit 026f9fc:
171 antirez in commit 11523b3:
175 antirez in commit f5a7f4f:
179 antirez in commit 4c6ff74:
180 Make tcp-keepalive default to 300 in internal conf.
183 antirez in commit 27dbec2:
184 In Redis RDB check: more details in error reportings.
187 antirez in commit 41f3004:
191 antirez in commit 278fe3e:
195 antirez in commit a117dfa:
196 Added a trivial program to randomly corrupt RDB files in /utils.
199 antirez in commit f5110c3:
203 antirez in commit 35b18bf:
207 antirez in commit f578f08:
211 tielei in commit 7f1e1ca:
215 antirez in commit 7a3a595:
219 antirez in commit c75ca10:
223 antirez in commit 2c3fcf8:
227 antirez in commit 7041967:
240 you the details, but the main things addressed in this release are the
243 1. A critical bug in Sentinel was hopefully fixed. During the big 3.2
244 refactoring of Redis Sentinel, in order to implement connection sharing
247 commands in the Redis link. This in turn resulted into an inability to talk
260 change in the jemalloc configuration did not really survived when the
267 7. A bug was fixed in redis-cli, that connected to the instance running on the
271 connections problems without resulting in any practical change in otherwise
276 And of course, more minor things that you can read in the detailed log
277 below. There are still reported bugs for 3.2 that were not fixed in this
305 Was introduced in Redis 3.2 new Sentinel connection sharing feature
309 @sskorgal for investigating the issue in depth.
356 code in to `rdb.c` appears to be capable as always to restore data from
358 current version in order to correctly restore data, is while loading the
359 opcodes, not the values itself as it happens in the case of RESTORE.
402 | check WRONGTYPE in BITFIELD before looping on the operations.
414 | fix crash in BITFIELD GET on non existing key or wrong type see #3259
419 this was a bug in the recent refactoring: bee963c4459223d874e3294a0d8638a588d33c8e
520 | Geo: fix typo in geohashEstimateStepsByRadius().
541 | Avoid undefined behavior in BITFIELD implementation.
548 apparently possible to write it in a more correct way.
597 | Fixed typo in Sentinel compareSlavesForPromotion() comment.
617 | fix pidfile in redis.conf
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
732 Use the COMMAND output to fill with partial information the built-in
735 in the help.h file when the redis-cli binary was compiled.
761 interested in the details.
769 * There was a problem in the way a cluster instance loaded the AOF that
786 * Redis Cluster replicas migration now works in a slightly different way. In
788 in the past (and if there was still trace of this information). Now instead
789 if a new slave gets at least a slot, and at least one other master in the
794 * CLUSTER SLOTS output now includes the node ID (in a backward compatible
797 * A lot of bug fixes you can read in the commits details below, with the
801 however do your tests before putting it into production in your environemnt
925 Fix issue in case the redirect address is in ipv6 format. Parse from behind to extract last part of…
945 | Quick fix to avoid false positive in replica migration test.
983 | Fixed typo in README.md
1013 | Minor redis-cli wording change in --help output.
1109 | fix small issues in redis 3.2
1166 no way to tell it had slaves in the past.
1168 This fix leaves the algorithm used in the past untouched, but adds a
1170 are assigend with their first slot, if other masters in the cluster have
1267 to the event *start time*. So if the event takes, in order to run, more
1319 | Fix typo in bitops.tcl comment.
1355 We want to report the original command in the stats, for example GEOADD,
1409 A similar command was imagined a few times in the past, but for
1411 Finally the command was proposed again in a clear form by
1441 | Fixes a typo in a comment
1466 Send a long double or double as a bulk reply, in a human friendly
1520 | Remove Lua state reference from buffers in lua_cmsgpack.
1530 | cmsgpack: pass correct osize values to lua allocator, update correct buf free space in cmsgpack
1560 | Typo ASII -> ASCII fixed in comment.
1570 | Cluster: include node IDs in SLOTS output.
1575 CLUSTER SLOTS now includes IDs in the nodes description associated with
1577 to reference a node in an unique way, so they were relying on CLUSTER
1591 * [FIX] avg_ttl reporting in INFO improved. (Salvatore Sanfilippo)
1603 could handle errors in a faulty way leading to crashes or other
1615 always be free to move keys between nodes about open slots, in order
1624 called BUMPEPOCH was introduced in order to support new modes
1627 harder to run Redis in a configuration that is unsecure because no
1628 firewalling was used in order to protect Redis from external accesses.
1640 what's new in this release. In the next of the following weeks we'll test
1641 in depth every feature and we'll release new RCs as bugs are discovered
1655 (Initially implemented in a fork of Redis called "Ardb".
1665 This makes Redis more memory efficient in different use cases.
1677 savings and storage space in RDB gains (up to 10x sometimes).
1682 and in order to make the replication of a this class of commands,
1704 All the Redis Cluster changes in 3.2 were backported to 3.0, so there is
1705 technically nothing new for now in this release. The most important things
1720 * More things backported to Redis 3.0 in the past, so no longer news of 3.2.
1727 non-backward compatible changes introduced in the 3.2 release: