- 18 Apr, 2012 1 commit
-
-
antirez authored
just fieldobj itself as sentinel of the fact a field object is used or not, instead of using the filed length, that may be confusing both for people and for the compiler emitting a warning.
-
- 17 Apr, 2012 1 commit
-
-
antirez authored
lookupKeyByPattern() was implemented with a trick to speedup the lookup process allocating two fake Redis obejcts on the stack. However now that we propagate expires to the slave as DEL operations the lookup of the key may result into a call to expireIfNeeded() having the stack allocated object as argument, that may in turn use it to create the protocol to send to the slave. But since this fake obejcts are inherently read-only this is a problem. As a side effect of this fix there are no longer size limits in the pattern to be used with GET/BY option of SORT. See https://github.com/antirez/redis/issues/460 for bug details.
-
- 06 Apr, 2012 1 commit
-
-
jokea authored
-
- 04 Apr, 2012 1 commit
-
-
antirez authored
Structure field controlling the INFO field master_link_down_since_seconds initialized correctly to avoid strange INFO output at startup when a slave has yet to connect to its master.
-
- 30 Mar, 2012 2 commits
- 29 Mar, 2012 2 commits
-
-
Joseph Jang authored
occurs when two or more dbs are replicated and at least one of them is >db10
-
antirez authored
Fix for slaves chains. Force resync of slaves (simply disconnecting them) when SLAVEOF turns a master into a slave.
-
- 19 Mar, 2012 1 commit
-
-
antirez authored
-
- 18 Mar, 2012 9 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
More memory tests implemented. Default number of iterations lowered to a more acceptable value of 50.
-
antirez authored
-
antirez authored
Number of iteration of --test-memory is now 300 (several minutes per gigabyte). Memtest86 and Memtester links are also displayed while running the test.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 26 Feb, 2012 1 commit
-
-
antirez authored
redis-benchmark: backported the more capable version from the unstable branch (pipelining,run selected tests,fixes)
-
- 22 Feb, 2012 4 commits
-
-
antirez authored
Fix for issue #306, thanks to tchajed (on github) for the pull request. The original patch was reworked a bit.
-
antirez authored
-
antirez authored
-
antirez authored
zzlIsInRange() now is capable of handling empty sorted sets that may end inside the data set when loading very old RDB files produced by early-stage versions of Redis.
-
- 21 Feb, 2012 6 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 16 Feb, 2012 1 commit
-
-
antirez authored
-
- 15 Feb, 2012 8 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Fixes to c->reply_bytes computation, and debug messages to closely study the behavior of memory pressure + slaves + maxmemory + blocked slaves.
-
antirez authored
Precision of getClientOutputBufferMemoryUsage() greatily improved, see issue #327 for more information.
-
antirez authored
-
antirez authored
-
antirez authored
1) sendReplyToClient() now no longer stops transferring data to a single client in the case we are out of memory (maxmemory-wise). 2) in processCommand() the idea of we being out of memory is no longer the naive zmalloc_used_memory() > server.maxmemory. To say if we can accept or not write queries is up to the return value of freeMemoryIfNeeded(), that has full control about that. 3) freeMemoryIfNeeded() now does its math without considering output buffers size. But at the same time it can't let the output buffers to put us too much outside the max memory limit, so at the same time it makes sure there is enough effort into delivering the output buffers to the slaves, calling the write handler directly. This three changes are the result of many tests, I found (partially empirically) that is the best way to address the problem, but maybe we'll find better solutions in the future.
-
antirez authored
Initial version of c->reply_bytes implementation backported from unstable to 2.4, in order to apply issue 327 patches.
-
- 14 Feb, 2012 2 commits