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/incubator-skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new 0593fdd Update backend-cluster.md (#2192)
0593fdd is described below
commit 0593fdd948ef82042712d0ee483dd461b79695a8
Author: 吴晟 Wu Sheng <[email protected]>
AuthorDate: Tue Jan 22 10:40:30 2019 +0800
Update backend-cluster.md (#2192)
---
docs/en/setup/backend/backend-cluster.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/en/setup/backend/backend-cluster.md
b/docs/en/setup/backend/backend-cluster.md
index b811f0a..4ce144d 100644
--- a/docs/en/setup/backend/backend-cluster.md
+++ b/docs/en/setup/backend/backend-cluster.md
@@ -4,10 +4,11 @@ so you should need cluster management always in product env.
Backend provides several ways to do cluster management. Choose the one you
need/want.
-- [Zookeeper coordinator](#zookeeper-coordinator). Use Zookeeper to let
backend detects and communicates
+- [Zookeeper coordinator](#zookeeper-coordinator). Use Zookeeper to let
backend instance detects and communicates
with each other.
- [Kubernetes](#kubernetes). When backend cluster are deployed inside
kubernetes, you could choose this
by using k8s native APIs to manage cluster.
+- [Consul](#consul). Use Consul as backend cluster management implementor, to
coordinate backend instances.
## Zookeeper coordinator
@@ -54,4 +55,4 @@ cluster:
serviceName: ${SW_SERVICE_NAME:"SkyWalking_OAP_Cluster"}
# Consul cluster nodes, example: 10.0.0.1:8500,10.0.0.2:8500,10.0.0.3:8500
hostPort: ${SW_CLUSTER_CONSUL_HOST_PORT:localhost:8500}
-```
\ No newline at end of file
+```
