Port Layout:
| Member | Cluster Client Port | Cluster Peer Port | API Port |
|---|---|---|---|
| primary-001 | 12379 | 12380 | 12381 |
| primary-002 | 22379 | 22380 | 22381 |
| primary-003 | 32379 | 22380 | 32381 |
| secondary-004 | - | - | 42381 |
| secondary-005 | - | - | 52381 |
./start_cluster.shPlease notice only one server will listen the port 10080 successfully because the members are running on the same machine. But it's fine for the following demoing.
./create_objects.shThe create_objects.sh applies the operation creation for all the yaml files under config/.
It's fine that it applies objects which has already existed.
./update_objects.shThe update_objects.sh applies the operation update for all the yaml files under config/.
It's fine that it applies objects which don't exist.
The check_cluster_status.sh will list:
- all status of members.
- all objects.
- Using
curlto test the access-ability of applied services. - Using HTTP-based tool hey for stress-testing the applied services.
./stop_cluster.sh ./clean_cluster.shIt will ignore step-stop if members have stopped.
go run mirror.go
go run remote.goPlease notice we didn't start backend service in the scripts above, so we testers could observe the situation when the backend is not ready.