665 Commits

Author SHA1 Message Date
antirez
6bfd9d131d Cluster: Tcl cluster client: slots-nodes map and close method.
Now the client is able to actually run commands in a Redis Cluster
assuming the slots->nodes map is stable.
2014-05-02 10:56:02 +02:00
antirez
b865ad41c8 Cluster: Tcl cluster client: build nodes representation. 2014-05-02 10:19:28 +02:00
antirez
bbaddc42ae Cluster: Tcl cluster client: get nodes description. 2014-05-02 09:55:27 +02:00
antirez
03f3698b59 Cluster: Tcl cluster client key -> hashslot. 2014-04-30 18:55:28 +02:00
antirez
99eb3ba709 Cluster test: Tcl cluster library initial skeleton. 2014-04-30 15:47:19 +02:00
antirez
05caa55af7 Cluster test: check for state=ok after slot allocation. 2014-04-30 09:29:03 +02:00
antirez
0935d95c5e Cluster test: slots allocation. 2014-04-29 18:40:43 +02:00
antirez
604cfb81c0 Cluster test: use 20 instances.
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.
2014-04-29 16:20:43 +02:00
antirez
f21dee6537 Cluster / Sentinel test: instances count moved to run.tcl. 2014-04-29 16:17:15 +02:00
antirez
884ba0b897 Cluster test: config epoch conflict resolution. 2014-04-29 15:39:59 +02:00
antirez
8b8b76475d Cluster test: auto-discovery to form full mesh. 2014-04-29 15:00:11 +02:00
antirez
71a4f1ae00 Cluster test: check that every node has a different ID. 2014-04-29 10:42:32 +02:00
antirez
be4cf4d66c Cluster test: basic cluster nodes info access functions. 2014-04-29 10:42:17 +02:00
antirez
ba46f66826 Test: fixed scripting.tcl test false positive. 2014-04-24 21:44:32 +02:00
antirez
0d183da744 Redis Cluster test framework skeleton. 2014-04-24 18:01:41 +02:00
antirez
c102ad59e9 Sentinel test files / directories layout improved.
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.
2014-04-24 11:08:22 +02:00
antirez
1ce3a4ff64 Test: spawn_instance now supports additional config. 2014-04-24 10:50:51 +02:00
Salvatore Sanfilippo
d7a561fbc7 Merge pull request #1677 from mattsta/expire-before-delete
Check key expiration before deleting
2014-04-23 16:13:49 +02:00
yoav
c8adbd0799 Merge remote-tracking branch 'upstream/unstable' into unstable 2014-04-22 10:01:21 +03:00
antirez
ed2cc684ab Fuzzy test for ZREMRANGEBYLEX added. 2014-04-18 13:02:16 +02:00
antirez
531fbda313 PFCOUNT multi-key test added. 2014-04-18 12:36:33 +02:00
antirez
00e9dc8b75 Sorted set lex ranges stress tester. 2014-04-17 10:25:58 +02:00
antirez
cd35352677 Basic ZRANGEBYLEX / ZLEXCOUNT tests. 2014-04-17 00:08:11 +02:00
antirez
20d49e3ac9 More HyperLogLog tests. 2014-04-16 09:17:38 +02:00
antirez
cd73060972 PFMERGE fixed to work with sparse encoding. 2014-04-14 16:09:32 +02:00
Matt Stancliff
daba106237 Add test for deleting an expired key
Verify proper expire-before-delete behavior.

This test passes with the expire-before-delete commit and fails
without it.
2014-04-10 18:32:19 -04:00
yoav
9af8168552 Fix eval usage in tests to conform with eval semantics 2014-04-06 17:20:01 +03:00
antirez
038f6c8221 Initial HyperLogLog tests. 2014-04-03 22:16:05 +02:00
antirez
947e9d4d98 Test: do not complain when "leaks" can't run because process died. 2014-03-25 09:33:37 +01:00
antirez
ebdf5ddfa9 Sentinel test: 02 unit better coverage + refactoring. 2014-03-18 15:18:51 +01:00
antirez
c870142fca Sentinel test: foreach_instance_id implements 'break'. 2014-03-18 15:06:52 +01:00
antirez
d9148d9fde Sentinel: instance_is_killed proc added to sentinel.tcl. 2014-03-18 14:58:27 +01:00
antirez
50d43b10d9 Sentinel test: set less time sensitive defaults.
This commit sets the failover timeout to 30 seconds instead of the 180
seconds default, and allows to reconfigure multiple slaves at the same
time.

This makes tests less sensible to timing, with the result that there are
less false positives due to normal behaviors that require time to
succeed or to be retried.

However the long term solution is probably some way in order to detect
when a test failed because of timing issues (for example split brain
during leader election) and retry it.
2014-03-04 17:10:29 +01:00
antirez
77298419f2 Sentinel test: debugging console improved. 2014-03-04 15:55:36 +01:00
antirez
d178f178e2 Sentinel test: initial debugging console. 2014-03-04 12:05:49 +01:00
antirez
5e30678074 Sentinel test: be more patient in create_redis_master_slave_cluster. 2014-03-04 11:20:53 +01:00
antirez
57e4555c2e Sentiel test: add test start time in output. 2014-03-04 11:17:27 +01:00
antirez
ce36a9e511 Sentinel test: use 1000 as retry in initial 00 unit test. 2014-03-03 13:26:18 +01:00
antirez
0af9090c4e Sentinel test: initial tests in 03 unit. 2014-03-03 13:25:14 +01:00
antirez
9a5d9f47f6 Sentinel test: foreach_instance_id now supports 'continue'. 2014-03-03 13:23:32 +01:00
antirez
144b3044a8 Sentienl test: fixed typo in unit 03 top comment. 2014-03-03 13:01:11 +01:00
antirez
4aa6b6e9b8 BITPOS fuzzy testing. 2014-02-27 15:27:05 +01:00
antirez
0348a8c1f8 Basic BITPOS tests. 2014-02-27 15:01:45 +01:00
antirez
411d930529 Added two more BITCOUNT tests stressing misaligned access. 2014-02-27 10:07:29 +01:00
antirez
ef3d34c345 BITCOUNT fuzzy test with random start/end added.
It was verified in practice that this test is able to stress much more
the implementation by introducing errors that were only trivially to
detect with different offsets but impossible to detect starting always
at zero and counting bits the full length of the string.
2014-02-27 10:00:17 +01:00
antirez
da7d4088c5 Sentinel test: add stub for unit 04. 2014-02-25 15:36:51 +01:00
antirez
eb282315ff Sentinel test: added TODO items in 02 unit. 2014-02-25 15:21:53 +01:00
antirez
808c9c16a9 Sentinel test: check role at end of unit 01. 2014-02-25 14:59:36 +01:00
antirez
ed309a8162 Sentinel test: kill masters instead of using DEBUG SLEEP in all tests. 2014-02-25 14:33:44 +01:00
antirez
9edf4e7c92 Sentinel test: restart instances left killed by previous unit.
An unit can abort in the middle for an error. The next unit should not
assume that the instances are in a clean state, and must restart what
was left killed.
2014-02-25 08:48:46 +01:00