You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by wu...@apache.org on 2019/09/27 13:25:23 UTC
[skywalking] branch master updated: Update backend-cluster.md
(#3536)
This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new 13ff55f Update backend-cluster.md (#3536)
13ff55f is described below
commit 13ff55fb6f4bdaa9d2d47bfe60e8290d148af397
Author: panjuan <pa...@apache.org>
AuthorDate: Fri Sep 27 21:25:14 2019 +0800
Update backend-cluster.md (#3536)
Modify `hot` to `host`
---
docs/en/setup/backend/backend-cluster.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/en/setup/backend/backend-cluster.md b/docs/en/setup/backend/backend-cluster.md
index 9f50fc7..0e7904f 100644
--- a/docs/en/setup/backend/backend-cluster.md
+++ b/docs/en/setup/backend/backend-cluster.md
@@ -43,7 +43,7 @@ Note:
- If set `schema` as `digest`, the password of expression is set in **clear text**.
In some cases, oap default gRPC host and port in core are not suitable for internal communication among the oap nodes.
-The following setting are provided to set the hot and port manually, based on your own LAN env.
+The following setting are provided to set the host and port manually, based on your own LAN env.
- internalComHost, the host registered and other oap node use this to communicate with current node.
- internalComPort, the port registered and other oap node use this to communicate with current node.
@@ -91,7 +91,7 @@ cluster:
Same as Zookeeper coordinator,
in some cases, oap default gRPC host and port in core are not suitable for internal communication among the oap nodes.
-The following setting are provided to set the hot and port manually, based on your own LAN env.
+The following setting are provided to set the host and port manually, based on your own LAN env.
- internalComHost, the host registered and other oap node use this to communicate with current node.
- internalComPort, the port registered and other oap node use this to communicate with current node.
@@ -118,4 +118,4 @@ cluster:
serviceName: ${SW_SERVICE_NAME:"SkyWalking_OAP_Cluster"}
#etcd cluster nodes, example: 10.0.0.1:2379,10.0.0.2:2379,10.0.0.3:2379
hostPort: ${SW_CLUSTER_ETCD_HOST_PORT:localhost:2379}
-```
\ No newline at end of file
+```