- 04 Jun, 2014 1 commit
-
-
antirez authored
-
- 26 May, 2014 3 commits
-
-
antirez authored
-
Matt Stancliff authored
Previously the PID format was: [PID] Timestamp But it recently changed to: PID:X Timestamp The tcl testing framework was grabbing the PID from \[\d+\], but that's not valid anymore. Now we grab the pid from "PID: <PID>" in the part of Redis startup output to the right of the ASCII logo.
-
antirez authored
FLUSHALL will fail on read-only slaves, but there the command is not needed in order to reset the instance with CLUSTER RESET so errors can be ignored.
-
- 23 May, 2014 5 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Do things in a sequence that prevents failover during failure detection.
-
antirez authored
The bug was triggered by running the test with Valgrind (which is a lot slower and more sensible to timing issues) after the recent changes that made Redis more promptly able to reply with the -LOADING error.
-
antirez authored
-
- 20 May, 2014 8 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Better handling of connection errors in order to update the table and recovery, populate the startup nodes table after fetching the list of nodes. More work to do about it, it is still not as reliable as redis-rb-cluster implementation which is the minimal reference implementation for Redis Cluster clients.
-
antirez authored
-
- 19 May, 2014 1 commit
-
-
antirez authored
-
- 07 May, 2014 2 commits
-
-
antirez authored
SPOP, tested in the new test, is among the commands rewritng the client->argv argument vector (it gets rewritten as SREM) for command replication purposes. Because of recent optimizations to client->argv caching in the context of the Lua internal Redis client, it is important to test for SPOP to be callable from Lua without bad effects to the other commands.
-
antirez authored
Sometimes the process is still there but no longer in a state that can be checked (after being killed). This used to happen after a call to SHUTDOWN NOSAVE in the scripting unit, causing a false positive.
-
- 05 May, 2014 15 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Now the client is able to actually run commands in a Redis Cluster assuming the slots->nodes map is stable.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
This makes tests a bit slower, but it is better to test things at a decent scale instead of using just a few nodes, and for a few tests we actually need so many nodes.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 28 Apr, 2014 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
The test now runs in a self-contained directory. The general abstractions to run the tests in an environment where mutliple instances are executed at the same time was extrapolated into instances.tcl, that will be reused to test Redis Cluster.
-
antirez authored
-
- 23 Apr, 2014 1 commit
-
-
Matt Stancliff authored
Verify proper expire-before-delete behavior. This test passes with the expire-before-delete commit and fails without it.
-