Functional test of redisgraph multi active design scheme

This document is mainly aimed at RedisGraph Function test of multi activity design scheme , To illustrate that the scheme is feasible .

See the previous article for the design document of this scheme RedisGraph Graphic database flexible design scheme

• Preparation conditions for function test
• RedisGraph The environmental preparation of one master, two slaves and three sentinels
• This time is mainly a high availability function test
• Resource Planning

• Open the sentry

docker exec -it dc1d79b6977f /bin/bash
redis-cli -p 26379

Copy

• Execute to view the master node information

sentinel master mymaster

Copy

• View slave node information

sentinel slaves mymaster

Copy

1)  1) "name"
    2) "172.25.0.4:6380"
    3) "ip"
    4) "172.25.0.4"
    5) "port"
    6) "6380"
    7) "runid"
    8) "44df8f11fb77d388e9f7dc83ab626c592a5a256d"
    9) "flags"
   10) "slave"
   11) "link-pending-commands"
   12) "0"
   13) "link-refcount"
   14) "1"
   15) "last-ping-sent"
   16) "0"
   17) "last-ok-ping-reply"
   18) "287"
   19) "last-ping-reply"
   20) "287"
   21) "down-after-milliseconds"
   22) "60000"
   23) "info-refresh"
   24) "8834"
   25) "role-reported"
   26) "slave"
   27) "role-reported-time"
   28) "510641"
   29) "master-link-down-time"
   30) "0"
   31) "master-link-status"
   32) "ok"
   33) "master-host"
   34) "redisgraph-master"
   35) "master-port"
   36) "6379"
   37) "slave-priority"
   38) "100"
   39) "slave-repl-offset"
   40) "100353"
   41) "replica-announced"
   42) "1"
2)  1) "name"
    2) "172.25.0.3:6381"
    3) "ip"
    4) "172.25.0.3"
    5) "port"
    6) "6381"
    7) "runid"
    8) "6baf5539d0430f737004c10afd0753722222c597"
    9) "flags"
   10) "slave"
   11) "link-pending-commands"
   12) "0"
   13) "link-refcount"
   14) "1"
   15) "last-ping-sent"
   16) "0"
   17) "last-ok-ping-reply"
   18) "287"
   19) "last-ping-reply"
   20) "287"
   21) "down-after-milliseconds"
   22) "60000"
   23) "info-refresh"
   24) "8834"
   25) "role-reported"
   26) "slave"
   27) "role-reported-time"
   28) "510682"
   29) "master-link-down-time"
   30) "0"
   31) "master-link-status"
   32) "ok"
   33) "master-host"
   34) "redisgraph-master"
   35) "master-port"
   36) "6379"
   37) "slave-priority"
   38) "100"
   39) "slave-repl-offset"
   40) "100353"
   41) "replica-announced"
   42) "1"

Copy

• Simulate primary node downtime

docker-compose stop
redisgraph-master

Copy

• View master node information

127.0.0.1:26379> SENTINEL get-master-addr-by-name mymaster

Copy

• The primary node has been transferred

• Start the down host

docker-compose start redisgraph-master

Copy

• View the current master node information

127.0.0.1:26379> SENTINEL get-master-addr-by-name mymaster

Copy

• When the down node starts , It does not affect the currently elected master node
• View master node information

info replication 

Copy

• You can see the previous master node (172.25.0.2) Transfer to slave node
• A functional test
• establish

127.0.0.1:6380> GRAPH.QUERY MotoGP "CREATE (:Rider {name:'Valentino Rossi'})-[:rides]->(:Team {name:'Yamaha'}), (:Rider {name:'Dani Pedrosa'})-[:rides]->(:Team {name:'Honda'}), (:Rider {name:'Andrea Dovizioso'})-[:rides]->(:Team {name:'Ducati'})"

Copy

• Inquire about

127.0.0.1:6380> GRAPH.QUERY MotoGP "MATCH (r:Rider)-[:rides]->(t:Team) WHERE t.name = 'Yamaha' RETURN r.name, t.name"

Copy

• Lord

• from

Remember to pay attention to , Communication is not lost