- 28 3月, 2012 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Premysl Hruby 提交于
-
- 25 3月, 2012 1 次提交
-
-
由 antirez 提交于
This new field counts all the times Redis is configured with AOF enabled and fsync policy 'everysec', but the previous fsync performed by the background thread was not able to complete within two seconds, forcing Redis to perform a write against the AOF file while the fsync is still in progress (likely a blocking operation).
-
- 22 3月, 2012 1 次提交
-
-
由 antirez 提交于
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.
-
- 14 3月, 2012 2 次提交
- 10 3月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 08 3月, 2012 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
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.
-
由 antirez 提交于
clusterGetRandomName() generalized into getRandomHexChars() so that we can use it for the run_id field as well.
-
由 antirez 提交于
By default Redis refuses writes with an error if the latest BGSAVE failed (and at least one save point is configured). However people having good monitoring systems may prefer a server that continues to work, since they are notified that there are problems by their monitoring systems. This commit implements the ability to turn the feature on or off via redis.conf and CONFIG SET.
-
- 07 3月, 2012 3 次提交
-
-
由 antirez 提交于
Redis now refuses accepting write queries if RDB persistence is configured, but RDB snapshots can't be generated for some reason. The status of the latest background save operation is now exposed in the INFO output as well. This fixes issue #90.
-
由 antirez 提交于
Better MONITOR output, now includes client ip:port or the lua string if the command was executed by the scripting engine.
-
由 antirez 提交于
-
- 29 2月, 2012 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
The new code uses a more generic data structure to describe redis operations. The new design allows for multiple alsoPropagate() calls within the scope of a single command, that is useful in different contexts. For instance there when there are multiple clients doing BRPOPLPUSH against the same list, and a variadic LPUSH is performed against this list, the blocked clients will both be served, and we should correctly replicate multiple LPUSH commands after the replication of the current command.
-
由 antirez 提交于
Added a new API to replicate an additional command after the replication of the currently executed command, in order to propagte the LPUSH originating from RPOPLPUSH and indirectly by BRPOPLPUSH.
-
- 28 2月, 2012 2 次提交
- 06 2月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 04 2月, 2012 2 次提交
-
-
由 antirez 提交于
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 提交于
Use less memory when emitting the protocol, by using more shared objects for commonly emitted parts of the protocol.
-
- 02 2月, 2012 2 次提交
- 01 2月, 2012 1 次提交
-
-
由 antirez 提交于
SORT is now more deterministic: does not accept to compare by score items that have scores not representing a valid double. Also items with the same score are compared lexycographically. At the same time the scripting side introduced the ability to sort the output of SORT when sort uses the BY <constant> optimization, resulting in no specific ordering. Since in this case the user may use GET, and the result of GET can be null, converted into false as Lua data type, this commit also introduces the ability to sort Lua tables containining false, only if the first (faster) attempt at using just table.sort with a single argument fails.
-
- 31 1月, 2012 2 次提交
-
-
由 antirez 提交于
Order output of commands returning random arrays using table.sort when called from Lua, partially fixing issue #165. The issue is yet not completely fixed since we can't add the REDIS_CMD_SORT_FOR_SCRIPT flag in SORT currently, both because it may contain NULLs and because it is not cool to re-sort everything at every call when instead this should be sorted only if BY <constant> is used.
-
由 antirez 提交于
-
- 24 1月, 2012 2 次提交
-
-
由 antirez 提交于
Client output buffer limits: configuration of parameters for the different classes of clients implemented.
-
由 antirez 提交于
asyncCloseClientOnOutputBufferLimitReached() now ignores clients with REDIS_CLOSE_ASAP flag already set. Return value of the function changed from int to void since it is not used. Fixed logging of the client scheduled to be closed.
-
- 23 1月, 2012 1 次提交
-
-
由 antirez 提交于
Implementation of the internals that make possible to terminate clients overcoming configured output buffer (soft and hard) limits.
-
- 20 1月, 2012 2 次提交
- 17 1月, 2012 2 次提交
- 12 1月, 2012 1 次提交
-
-
由 antirez 提交于
On crash print information about the current client (if any), command vector, and object associated to first argument assuming it is a key.
-
- 03 1月, 2012 1 次提交
-
-
由 Pieter Noordhuis 提交于
-
- 31 12月, 2011 3 次提交