- 30 Aug, 2012 1 commit
-
-
antirez authored
This change is required to make Redis 2.4 compatible with Sentinel. The Run ID is a field that identifies a single execution of the Redis server. It can be useful for many purposes as it makes easy to detect if the instance we are talking about is the same, or if it is a different one or was rebooted. An application of run_id will be in the partial synchronization of replication, where a slave may request a partial sync from a given offset only if it is talking with the same master. Another application is in failover and monitoring scripts.
-
- 09 Jul, 2012 1 commit
-
-
antirez authored
The REPLCONF command is an internal command (not designed to be directly used by normal clients) that allows a slave to set some replication related state in the master before issuing SYNC to start the replication. The initial motivation for this command, and the only reason currently it is used by the implementation, is to let the slave instance communicate its listening port to the slave, so that the master can show all the slaves with their listening ports in the "replication" section of the INFO output. This allows clients to auto discover and query all the slaves attached into a master. Currently only a single option of the REPLCONF command is supported, and it is called "listening-port", so the slave now starts the replication process with something like the following chat: REPLCONF listening-prot 6380 SYNC Note that this works even if the master is an older version of Redis and does not understand REPLCONF, because the slave ignores the REPLCONF error. In the future REPLCONF can be used for partial replication and other replication related features where there is the need to exchange information between master and slave. NOTE: This commit also fixes a bug: the INFO outout already carried information about slaves, but the port was broken, and was obtained with getpeername(2), so it was actually just the ephemeral port used by the slave to connect to the master as a client.
-
- 12 May, 2012 2 commits
-
-
antirez authored
-
antirez authored
If a large amonut of keys are all expiring about at the same time, the "active" expired keys collection cycle used to block as far as the percentage of already expired keys was >= 25% of the total population of keys with an expire set. This could block the server even for many seconds in order to reclaim memory ASAP. The new algorithm uses at max a small amount of milliseconds per cycle, even if this means reclaiming the memory less promptly it also means a more responsive server.
-
- 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