- 21 Mar, 2012 1 commit
-
-
antirez authored
-
- 20 Mar, 2012 3 commits
-
-
antirez authored
DEBUG should not be flagged as w otherwise we can not call DEBUG DIGEST and other commands against read only slaves.
-
antirez authored
This commit introduces support for read only slaves via redis.conf and CONFIG GET/SET commands. Also various semantical fixes are implemented here: 1) MULTI/EXEC with only read commands now work where the server is into a state where writes (or commands increasing memory usage) are not allowed. Before this patch everything inside a transaction would fail in this conditions. 2) Scripts just calling read-only commands will work against read only slaves, when the server is out of memory, or when persistence is into an error condition. Before the patch EVAL always failed in this condition.
-
antirez authored
-
- 19 Mar, 2012 3 commits
- 18 Mar, 2012 4 commits
-
-
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
-
- 16 Mar, 2012 3 commits
- 15 Mar, 2012 1 commit
-
-
antirez authored
Use a simple protocol between clientsCron() and helper functions to understand if the client is still valind and clientsCron() should continue processing or if the client was freed and we should continue with the next one.
-
- 14 Mar, 2012 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
The new function is used in order to resize the string allocation so that only the minimal allocation possible is used, removing all the free space at the end of the string normally used to improve efficiency of concatenation operations.
-
antirez authored
-
- 13 Mar, 2012 7 commits
-
-
antirez authored
-
antirez authored
Process async client checks like client timeouts and BLPOP timeouts incrementally using a circular list.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
RDB hashes loading, fixed another bug in the loading of HT-encoded hashes: when the hash entry is too big for ziplist, add the field, then convert. The code used to break before the new entry was inserted, resulting into missing fields in the loaded Hash object.
-
antirez authored
RDB hashes loading fixed removing the assertion that failed every time an HT-encoded hash was loaded.
-
- 10 Mar, 2012 10 commits
-
-
Salvatore Sanfilippo authored
fix typo of redis.conf
-
quiver authored
-
antirez authored
-
antirez authored
-
antirez authored
RDB version is no 4, because small hashes are now encoded as ziplists, so older versions of Redis will not understand this format.
-
antirez authored
-
antirez authored
-
antirez authored
Minor code aesthetic change to use Redis code base style rule of saving vertical space when possible.
-
antirez authored
Removed handling of deprecated hash-max-zipmap-entries nad hash-map-zipmap-value. Pieter is too good with users ;). Better to have them switch to a saner configuration ASAP after the 2.6 upgrade.
-
antirez authored
Added a top-function comment to rioWriteHashIteratorCursor() to better specify what the function does. Not immediately clear from the name.
-
- 09 Mar, 2012 1 commit
-
-
antirez authored
-
- 08 Mar, 2012 3 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
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.
-