- 28 3月, 2012 2 次提交
-
-
由 Premysl Hruby 提交于
-
由 Premysl Hruby 提交于
-
- 27 3月, 2012 1 次提交
-
-
由 antirez 提交于
SIGSEGV handler refactored so that we can reuse stack trace and current client logging functionalities in other contexts.
-
- 25 3月, 2012 4 次提交
-
-
由 antirez 提交于
-
由 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).
-
由 antirez 提交于
-
由 antirez 提交于
Apparently because the sample RDB file was not copied before every test Redis had a chance to replace it with a newly written one, so that the next test could fail.
-
- 24 3月, 2012 7 次提交
- 23 3月, 2012 5 次提交
- 22 3月, 2012 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
DEBUG should not be flagged as w otherwise we can not call DEBUG DIGEST and other commands against read only slaves.
-
由 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.
-
- 20 3月, 2012 6 次提交
- 19 3月, 2012 4 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
More memory tests implemented. Default number of iterations lowered to a more acceptable value of 50.
-
由 antirez 提交于
-
由 antirez 提交于
Number of iteration of --test-memory is now 300 (several minutes per gigabyte). Memtest86 and Memtester links are also displayed while running the test.
-
- 18 3月, 2012 4 次提交
- 16 3月, 2012 1 次提交
-
-
由 antirez 提交于
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 3月, 2012 2 次提交