summaryrefslogtreecommitdiff
path: root/tests/cluster
Commit message (Collapse)AuthorAgeFilesLines
* TLS: Connections refactoring and TLS support.Yossi Gottlieb2019-10-073-0/+7
| | | | | | | | * Introduce a connection abstraction layer for all socket operations and integrate it across the code base. * Provide an optional TLS connections implementation based on OpenSSL. * Pull a newer version of hiredis with TLS support. * Tests, redis-cli updates for TLS support.
* cluster.tcl: Add master consecutively down test.WuYunlong2018-06-301-0/+77
|
* Cluster tests now using redis-cli instead of redis-tribartix2018-04-232-12/+12
|
* Cluster: add test for the nofailover flag.antirez2018-03-142-0/+71
|
* Cluster test 12: reshard back just a few slots to speedup the test.antirez2016-05-051-7/+7
|
* Quick fix to avoid false positive in replica migration test.antirez2016-05-051-1/+4
|
* Cluster regression test for #3043.antirez2016-05-021-0/+61
| | | | | | The test works but is very slow so far, since it involves resharding 1/5 of all the cluster slots from master 0 to the other 4 masters and back into the original master.
* Cluster: resharding test provides more state when failing.antirez2016-02-171-3/+8
| | | | | | | Now elements added to lists are incremental numbers in order to understand, when inconsistencies are found, what is the order in which the elements were added. Also the error now provides both the expected and found value.
* Cluster: verify slaves consistency after resharding.antirez2015-12-181-0/+23
|
* Cluster: resharding test now checks AOF consistency.antirez2015-12-171-0/+42
| | | | | | It's a key invariant that when AOF is enabled, after the cluster reshards, a crash-recovery event causes all the keys to be still fine with the expected logical content. Now this is part of unit 04.
* Cluster: more reliable migration tests.antirez2015-12-101-43/+24
| | | | | | | | The old version was modeled with two failovers, however after the first it is possible that another slave will migrate to the new master, since for some time the new master is not backed by any slave. Probably there should be some pause after a failover, before the migration. Anyway the test is simpler in this way, and depends less on timing.
* Cluster: more reliable replicas migration test.antirez2015-12-101-0/+75
|
* Sentinel / Cluster test: exit with non-zero error code on failures.antirez2015-03-301-0/+1
|
* Cluster: unit 10 modified to leave cluster in proper state.antirez2015-03-221-0/+5
|
* Cluster: CLUSTER FAILOVER TAKEOVER tests.antirez2015-03-221-0/+59
|
* Cluster: more tests for manual failover + FORCE.antirez2015-03-221-1/+93
|
* Cluster: new tests1 for manual failover and scripts replication.antirez2015-03-221-0/+95
|
* Cluster test: when valgrind is enabled, use a larger node-timeout.antirez2015-01-221-1/+6
| | | | Removes some percentage of timing related failures.
* Cluster test initialization: use transaction for reset + set-config-epoch.antirez2015-01-211-0/+2
| | | | | Otherwise between the two commands other nodes may contact us making the next SET-CONFIG-EPOCH call impossible.
* Cluster/Sentinel test: pause on exceptions as well.antirez2015-01-211-0/+1
|
* Cluster test: also write from Lua script in resharding test.antirez2015-01-091-2/+11
|
* Cluster test: helpers/onlydots.tcl: detect EOF and exit.antirez2014-10-081-1/+3
|
* Cluster test: less console-spammy resharding test.antirez2014-10-082-2/+19
|
* Remove trailing spaces from testsMatt Stancliff2014-09-291-1/+1
|
* Fix spelling in some test casesMatt Stancliff2014-09-291-1/+1
|
* Spell software correctlyMatt Stancliff2014-09-292-2/+2
|
* Cluster test: unit 09, Pub/Sub across the cluster.antirez2014-09-151-0/+40
|
* Cluster test: unit 08, update messages.antirez2014-09-151-0/+90
|
* Cluster test: unit 07, replicas migration.antirez2014-07-281-0/+47
|
* Cluster test: unit 06 cluster creation comment fixed.antirez2014-07-281-2/+1
|
* Cluster test: node reachability condition fixed.antirez2014-07-251-1/+2
|
* Cluster test: init test, be patient during restarts.antirez2014-07-251-2/+7
|
* Cluster test: 03 unit speedup, don't send WAIT to slaves.antirez2014-07-251-2/+5
|
* Cluster test: unit 06, slaves with stale data can't failover.antirez2014-07-252-0/+75
|
* Cluster test: new unit 05, slave selection.antirez2014-07-251-0/+94
|
* Cluster test: use larger keyspace in resharding test.antirez2014-07-211-1/+1
|
* Cluster test: unit 04, consistency during resharding.antirez2014-07-211-0/+90
|
* Cluster test: test that writes are retained during failovers.antirez2014-07-181-2/+13
| | | | | | | | In the test we use WAIT when the master and slave are up, and only later the partition is created killing the master, so we are sure we don't incur in failure modes that may lose writes in this test: the goal here is to make sure that the elected slave was replicating correctly with the master.
* Add correct exit value to failed testsMatt Stancliff2014-06-181-0/+1
|
* Cluser test: write multiple keys in unit 03.antirez2014-06-111-4/+8
| | | | | The write-failover-read test is better if we write 100 keys so that we are sure all the nodes are affected by the write.
* Cluster test: rewrite config when resetting nodes.antirez2014-06-111-1/+2
|
* Cluster test: set config epochs when creating clusters.antirez2014-06-101-0/+1
|
* Cluster test: unit 03, check epochs correctness.antirez2014-06-101-0/+6
|
* Cluster test: better failover detection in unit 03.antirez2014-06-101-5/+17
|
* Cluster test: new unit 03, failover loop stress testing.antirez2014-06-101-0/+79
|
* Cluster test: 02 unit more reliable waiting for slave sync.antirez2014-06-101-0/+8
|
* Cluster test: unit 02 should wait for failover.antirez2014-06-101-0/+10
|
* Cluster test: check master -> slave role switch.antirez2014-06-101-0/+12
|
* Cluster test: add tmp dir to Git repo.antirez2014-05-261-0/+2
|
* Cluster test: catch FLUSHALL errors on node reset.antirez2014-05-261-1/+1
| | | | | | 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.
View Lorry Controller Status