- 15 Feb, 2012 4 commits
-
-
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.
-
- 02 Feb, 2012 1 commit
-
-
antirez authored
-
- 12 Jan, 2012 1 commit
-
-
antirez authored
On crash print information about the current client (if any), command vector, and object associated to first argument assuming it is a key.
-
- 07 Jan, 2012 2 commits
-
-
antirez authored
Protections against protocol desyncs, leading to infinite query buffer growing, due to nul-terms in specific bytes of the request or indefinitely long multi bulk or bulk count strings without newlines. This bug is related to Issue #141 as well.
-
antirez authored
Fixed replication when multiple slaves are attaching at the same time. The output buffer was not copied correctly between slaves. This fixes issue #141.
-
- 24 Nov, 2011 3 commits
- 21 Nov, 2011 2 commits
- 11 Nov, 2011 2 commits
- 18 Oct, 2011 2 commits
-
-
Herbert G. Fischer authored
-
Herbert G. Fischer authored
-
- 10 Oct, 2011 1 commit
-
-
Nathan Florea authored
Added a configuration directive to allow a user to specify the permissions to be granted to the Unix socket file. I followed the format Pieter and Salvatore discusses in issue #85 ( https://github.com/antirez/redis/issues/85).
-
- 19 Sep, 2011 2 commits
- 12 Jul, 2011 3 commits
-
-
antirez authored
-
antirez authored
Take a pointer to the relevant entry of the command table in the client structure. This is generally a more sounding design, simplifies a few functions prototype, and as a side effect fixes a bug related to the conversion of EXPIRE -1 to DEL: before of this fix Redis tried to convert it into an EXPIREAT in the AOF code, regardless of our rewrite of the command.
-
antirez authored
dataspace change hook functions backported to 2.4. They are just wrappers at this point but this makes simpler to cherry-pick between branches.
-
- 01 Jul, 2011 2 commits
- 17 Jun, 2011 1 commit
-
-
antirez authored
-
- 14 Jun, 2011 1 commit
-
-
antirez authored
-
- 10 Jun, 2011 1 commit
-
-
antirez authored
-
- 08 Jun, 2011 1 commit
-
-
antirez authored
INFO now contains the time (in usecs) needed to fork() in order to persist. The info is available in the stats section of INFO.
-
- 31 May, 2011 1 commit
-
-
antirez authored
-
- 30 May, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 22 May, 2011 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 19 May, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 27 Apr, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 21 Apr, 2011 2 commits
- 20 Apr, 2011 3 commits