This is an automated email from the ASF dual-hosted git repository.
littlecui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-service-center.git
The following commit(s) were added to refs/heads/master by this push:
new 4ddd84be [doc] fix syncer document reading problem (#1299)
4ddd84be is described below
commit 4ddd84be1c29782e1d98025fba7f28a8b6487f04
Author: robotljw <[email protected]>
AuthorDate: Tue Apr 19 19:26:50 2022 +0800
[doc] fix syncer document reading problem (#1299)
---
docs/user-guides/health.png | Bin 179768 -> 0 bytes
docs/user-guides/instance-az.png | Bin 0 -> 31674 bytes
docs/user-guides/syncer-deploy-architecture-2.png | Bin 0 -> 73120 bytes
docs/user-guides/syncer.md | 131 +++++++++++++++++-----
docs/user-guides/vm-deploy.png | Bin 0 -> 17006 bytes
5 files changed, 103 insertions(+), 28 deletions(-)
diff --git a/docs/user-guides/health.png b/docs/user-guides/health.png
deleted file mode 100644
index fa952683..00000000
Binary files a/docs/user-guides/health.png and /dev/null differ
diff --git a/docs/user-guides/instance-az.png b/docs/user-guides/instance-az.png
new file mode 100644
index 00000000..0e458eed
Binary files /dev/null and b/docs/user-guides/instance-az.png differ
diff --git a/docs/user-guides/syncer-deploy-architecture-2.png
b/docs/user-guides/syncer-deploy-architecture-2.png
new file mode 100644
index 00000000..defd12a9
Binary files /dev/null and b/docs/user-guides/syncer-deploy-architecture-2.png
differ
diff --git a/docs/user-guides/syncer.md b/docs/user-guides/syncer.md
index 7a1ed052..48e2872a 100644
--- a/docs/user-guides/syncer.md
+++ b/docs/user-guides/syncer.md
@@ -1,4 +1,4 @@
-# syncer
+# Syncer
Service-Center supports synchronization. If you want to use synchronization,
you can refer to the step.
@@ -12,16 +12,15 @@ Service-Center supports synchronization. If you want to use
synchronization, you
### deployment Architecture
-
+As shown in the figure below, etcd can be deployed as an independent cluster.
-| vm-ip | region |
-| -------------- |----------|
-| 192.168.81.128 | region-1 |
-| 192.168.81.129 | region-1 |
-| 192.168.81.130 | region-1 |
-| 192.168.81.131 | region-2 |
-| 192.168.81.132 | region-2 |
-| 192.168.81.133 | region-2 |
+
+
+It can also be deployed like this.
+
+
+
+
## installation operation
@@ -32,43 +31,119 @@ Refer to the official website
[documentation](https://etcd.io/docs/v3.5/op-guide
### install sc
> Note: Only the 2.1+ version of sc supports synchronization
-**first step**: modify the files in `conf`
+#### step 1
+modify the files in `conf`
`app.conf`: modify frontend_host_ip and httpaddr to the local ip address
-
+
+
+`app.yaml`:
+
+modify
+
+1. server.host
+2. REGISTRY_KIND
+3. REGISTRY_ETCD_CLUSTER_NAME
+4. REGISTRY_ETCD_CLUSTER_MANAGER_ENDPOINTS
+5. REGISTRY_ETCD_CLUSTER_ENDPOINTS
+6. registry.instance.datacenter.name
+7. registry.instance.datacenter.region
+8. registry.instance.datacenter.availableZone
-`app.yaml`: modify server.host, REGISTRY_KIND, REGISTRY_ETCD_CLUSTER_NAME,
REGISTRY_ETCD_CLUSTER_MANAGER_ENDPOINTS, REGISTRY_ETCD_CLUSTER_ENDPOINTS
+
-
-
+
+
+
`chassis.yaml`: modify listenAddress to the local ip address
-
+
`syncer.yaml`: turn on the enableOnStart switch, and modify endpoints, the sc
machine ip in region-2
-**second step**: repeat the above operation to modify the configuration of sc
on other machines
+#### step 2
-**third step**: start start-service-center.sh
+Repeat the above operation to modify the configuration of sc on other machines.
-sh `start-service-center.sh`
+#### step 3
-**the fourth step**: start start-frontend.sh
+```shell
+sh start-service-center.sh
+```
-sh `start-frontend.sh`
+#### step 4
-open the front-end interface of any node
+```shell
+sh start-frontend.sh
+```
-
-
+#### step 5
+Open the front-end interface of any node.
-### verify health
+
-curl -k http://{ip}:30100/health
-
+Instances in the peer region have been synchronized.
-> Congratulations！！！
+
+### verify health
+```shell
+curl -k http://{ip}:30100/health
+```
+
+```yaml
+{
+ "instances": [
+ {
+ "instanceId": "e810f2f3baf711ec9486fa163e176e7b",
+ "serviceId": "7062417bf9ebd4c646bb23059003cea42180894a",
+ "endpoints": [
+ "rest://[::]:30100/"
+ ],
+ "hostName": "etcd03",
+ "status": "UP",
+ "healthCheck": {
+ "mode": "push",
+ "interval": 30,
+ "times": 3
+ },
+ "timestamp": "1649833445",
+ "dataCenterInfo": {
+ "name": "dz1",
+ "region": "rg1",
+ "availableZone": "az1"
+ },
+ "modTimestamp": "1649833445",
+ "version": "2.1.0"
+ },
+ {
+ "instanceId": "e810f2f3baf711ec9486fa163e176e8b",
+ "serviceId": "7062417bf9ebd4c646bb23059003cea42180896a",
+ "endpoints": [
+ "rest://[::]:30100/"
+ ],
+ "hostName": "etcd04",
+ "status": "UP",
+ "healthCheck": {
+ "mode": "push",
+ "interval": 30,
+ "times": 3
+ },
+ "timestamp": "1649833445",
+ "dataCenterInfo": {
+ "name": "dz2",
+ "region": "rg2",
+ "availableZone": "az2"
+ },
+ "modTimestamp": "1649833445",
+ "version": "2.1.0"
+ }
+ ...
+ ]
+}
+```
+
+> Congratulations！！！
\ No newline at end of file
diff --git a/docs/user-guides/vm-deploy.png b/docs/user-guides/vm-deploy.png
new file mode 100644
index 00000000..de8f7061
Binary files /dev/null and b/docs/user-guides/vm-deploy.png differ
