Searched refs:instances (Results 1 – 7 of 7) sorted by relevance
2 instances configured to run in cluster mode. Its main goal is to allow manual4 unit tests, for example when a lot of instances are needed in order to trigger7 The tool can also be used just to easily create a number of instances in a16 number of instances you want to create.17 2. Use "./create-cluster start" in order to run the instances.20 4. Now you are ready to play with the cluster. AOF files and logs for each instances are created in…24 1. Use "./craete-cluster stop" to stop all the instances. After you stopped the instances you can u…
9 proc test_cluster_publish {instance instances} { argument11 for {set j 0} {$j < $instances} {incr j} {23 for {set j 0} {$j < $instances} {incr j} {
1332 di = dictGetIterator(instances); in getSentinelRedisInstanceByAddrAndRunID()1364 di = dictGetIterator(instances); in sentinelAddFlagsToDictOfRedisInstances()1378 di = dictGetIterator(instances); in sentinelDelFlagsToDictOfRedisInstances()2511 di = dictGetSafeIterator(instances); in sentinelForceHelloUpdateDictOfRedisInstances()2831 di = dictGetIterator(instances); in addReplyDictOfRedisInstances()2832 addReplyMultiBulkLen(c,dictSize(instances)); in addReplyDictOfRedisInstances()3914 int instances = 0; in sentinelSelectSlave() local3942 instance[instances++] = slave; in sentinelSelectSlave()3945 if (instances) { in sentinelSelectSlave()4266 void sentinelHandleDictOfRedisInstances(dict *instances) { in sentinelHandleDictOfRedisInstances() argument[all …]
364 proc foreach_instance_id {instances idvar code} {366 for {set id 0} {$id < [llength $instances]} {incr id} {
77 test {MIGRATE is able to migrate a key between two instances} {96 test {MIGRATE is able to copy a key between two instances} {
351 responsible for creating instances of the `redisReply` can be customized by
248 with certain Redis instances. A common result of this bug was the inability1592 * [FIX] Sentinel: improve handling of known Sentinel instances.