- 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.
-
- 29 Mar, 2012 1 commit
-
-
Joseph Jang authored
occurs when two or more dbs are replicated and at least one of them is >db10
-
- 18 Mar, 2012 5 commits
-
-
antirez authored
-
antirez authored
More memory tests implemented. Default number of iterations lowered to a more acceptable value of 50.
-
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
-
- 15 Feb, 2012 6 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
-
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.
-
- 02 Feb, 2012 2 commits
- 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.
-
- 10 Jan, 2012 1 commit
-
-
antirez authored
-
- 07 Jan, 2012 1 commit
-
-
antirez authored
-
- 28 Nov, 2011 1 commit
-
-
antirez authored
-
- 24 Nov, 2011 2 commits
- 21 Nov, 2011 1 commit
-
-
antirez authored
-
- 18 Oct, 2011 2 commits
-
-
Herbert G. Fischer authored
-
Herbert G. Fischer authored
-
- 14 Oct, 2011 1 commit
-
-
antirez authored
Ref: issue #103
-
- 10 Oct, 2011 4 commits
-
-
antirez authored
-
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).
-
Nathan Florea authored
-
antirez authored
-
- 20 Sep, 2011 4 commits
-
-
antirez authored
hash zipmap max entries and entry size information removed from INFO command since we have this info and the equivalent info for sets, hashes, zset accessible via the CONFIG GET command.
-
vambo authored
-
Konstantin Tokarev authored
Applied patch from Issue 119 provided by pahowes@gmail.com
-
antirez authored
-
- 19 Sep, 2011 1 commit
-
-
antirez authored
-
- 14 Sep, 2011 2 commits
- 13 Sep, 2011 1 commit
-
-
antirez authored
-
- 09 Aug, 2011 1 commit
-
-
antirez authored
Auto rewrite integer overflow fixed. Thanks to Gaurav for finding it (see issue 602 on google code), and Pieter Noordhuis for tracing it.
-
- 22 Jul, 2011 2 commits