- 15 2月, 2013 3 次提交
- 14 2月, 2013 4 次提交
- 05 2月, 2013 1 次提交
-
-
由 antirez 提交于
-
- 19 1月, 2013 1 次提交
-
-
由 guiquanz 提交于
-
- 14 11月, 2012 1 次提交
-
-
由 antirez 提交于
Now that we cache connections, a retry attempt makes sure that the operation don't fail just because there is an existing connection error on the socket, like the other end closing the connection. Unfortunately this condition is not detectable using getsockopt(SO_ERROR), so the only option left is to retry. We don't retry on timeouts.
-
- 13 11月, 2012 1 次提交
-
-
由 antirez 提交于
When a timeout <= 0 is provided we set a default timeout of 1 second. It was set to 1 millisecond for an error resulting from a recent change.
-
- 12 11月, 2012 2 次提交
-
-
由 antirez 提交于
While it is documented that the MIGRATE timeout is in milliseconds, it was in seconds instead. This commit fixes the problem.
-
由 antirez 提交于
By caching TCP connections used by MIGRATE to chat with other Redis instances a 5x performance improvement was measured with redis-benchmark against small keys. This can dramatically speedup cluster resharding and other processes where an high load of MIGRATE commands are used.
-
- 09 11月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 07 11月, 2012 2 次提交
-
-
由 antirez 提交于
With COPY now MIGRATE does not remove the key from the source instance. With REPLACE it uses RESTORE REPLACE on the target host so that even if the key already eixsts in the target instance it will be overwritten. The options can be used together.
-
由 antirez 提交于
The REPLACE option deletes an existing key with the same name (if any) and materializes the new one. The default behavior without RESTORE is to return an error if a key already exists.
-
- 24 8月, 2012 1 次提交
-
-
由 antirez 提交于
The previous implementation of zmalloc.c was not able to handle out of memory in an application-specific way. It just logged an error on standard error, and aborted. The result was that in the case of an actual out of memory in Redis where malloc returned NULL (In Linux this actually happens under specific overcommit policy settings and/or with no or little swap configured) the error was not properly logged in the Redis log. This commit fixes this problem, fixing issue #509. Now the out of memory is properly reported in the Redis log and a stack trace is generated. The approach used is to provide a configurable out of memory handler to zmalloc (otherwise the default one logging the event on the standard output is used).
-
- 24 4月, 2012 2 次提交
- 10 4月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 09 4月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 03 4月, 2012 2 次提交
- 02 4月, 2012 5 次提交
- 01 4月, 2012 1 次提交
-
-
由 antirez 提交于
-
- 08 3月, 2012 1 次提交
-
-
由 antirez 提交于
clusterGetRandomName() generalized into getRandomHexChars() so that we can use it for the run_id field as well.
-
- 25 1月, 2012 3 次提交
- 09 11月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 23 10月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 20 10月, 2011 1 次提交
-
-
由 antirez 提交于
-
- 17 10月, 2011 3 次提交
- 13 10月, 2011 1 次提交
-
-
由 antirez 提交于
-