You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by ni...@apache.org on 2019/08/09 09:41:45 UTC
[servicecomb-website] 01/02: Add a quick start case for mersher.
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-website.git
commit dddcfcb9f1e2012e95171b611277eea970b57349
Author: surechen <81...@qq.com>
AuthorDate: Fri Aug 9 14:35:15 2019 +0800
Add a quick start case for mersher.
---
_data/navigation.yml | 54 +++++--
_docs/cn/mersher-distributed-tracing.md | 48 +++++++
_docs/cn/mersher-flow-control.md | 45 ++++++
_docs/cn/mersher-load-balance.md | 36 +++++
_docs/cn/mersher-quick-start-advance.md | 24 ++++
_docs/cn/mersher-quick-start.md | 155 +++++++++++++++++++++
_docs/cn/mersher-service-management.md | 87 ++++++++++++
_docs/mersher-distributed-tracing.md | 54 +++++++
_docs/mersher-flow-control.md | 45 ++++++
_docs/mersher-load-balance.md | 38 +++++
_docs/mersher-quick-start-advance.md | 24 ++++
_docs/mersher-quick-start.md | 155 +++++++++++++++++++++
_docs/mersher-service-management.md | 87 ++++++++++++
.../images/mersher/mersher-circuitbreaker-ret.png | Bin 0 -> 5972 bytes
assets/images/mersher/mersher-circuitbreaker.png | Bin 0 -> 15220 bytes
assets/images/mersher/mersher-deployment.png | Bin 0 -> 78448 bytes
.../images/mersher/mersher-flow-control-fail.png | Bin 0 -> 26430 bytes
assets/images/mersher/mersher-flow-control-log.png | Bin 0 -> 36063 bytes
assets/images/mersher/mersher-flowchart.png | Bin 0 -> 26262 bytes
assets/images/mersher/mersher-intro.png | Bin 0 -> 14916 bytes
assets/images/mersher/mersher-ser-manage-ver.png | Bin 0 -> 5934 bytes
assets/images/mersher/mersher-servercenter.png | Bin 0 -> 31799 bytes
assets/images/mersher/mersher-testgohttp.png | Bin 0 -> 28156 bytes
assets/images/mersher/mersher-testinit.png | Bin 0 -> 29517 bytes
assets/images/mersher/mersher-testpythonhttp.png | Bin 0 -> 28040 bytes
assets/images/mersher/mersher-tracing-30108.png | Bin 0 -> 42437 bytes
assets/images/mersher/mersher-tracing-30111.png | Bin 0 -> 42725 bytes
assets/images/mersher/mersher-tracing-func.png | Bin 0 -> 30824 bytes
28 files changed, 842 insertions(+), 10 deletions(-)
diff --git a/_data/navigation.yml b/_data/navigation.yml
index ccb709d..eeb1dfa 100755
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -16,13 +16,15 @@ t:
url: /release/
docs:
- - title: "Quick Start"
+ - title: "Development of microservices application based on java microservice SDK"
url: /docs/quick-start/
- - title: "Develop microservice application in minutes"
- url: /docs/quick-start-bmi/
- - title: "Advance microservice development"
- url: /docs/quick-start-advance/
children:
+ - title: "Quick Start"
+ url: /docs/quick-start/
+ - title: "Develop microservice application in minutes"
+ url: /docs/quick-start-bmi/
+ - title: "Advance microservice development"
+ url: /docs/quick-start-advance/
- title: Load Balance
url: /docs/quick-start-advance/load-balance/
- title: Flow Control
@@ -31,6 +33,21 @@ t:
url: /docs/quick-start-advance/service-management/
- title: Distributed Tracing
url: /docs/quick-start-advance/distributed-tracing/
+ - title: "Use mersher to merge into the servicecomb microservice system"
+ url: /docs/mersher-quick-start/
+ children:
+ - title: "Quick Start"
+ url: /docs/mersher-quick-start/
+ - title: "Mersher Advance"
+ url: /docs/mersher-quick-start-advance/
+ - title: "Mersher balance"
+ url: /docs/mersher-quick-start-advance/mersher-load-balance/
+ - title: "Mersher Flow Control"
+ url: /docs/mersher-quick-start-advance/mersher-flow-control/
+ - title: "Mersher Service Management"
+ url: /docs/mersher-quick-start-advance/mersher-service-management/
+ - title: "Mersher Distributed Tracing"
+ url: /docs/mersher-quick-start-advance/mersher-distributed-tracing/
users:
- title: Java Chassis
children:
@@ -120,13 +137,15 @@ t:
url: /cn/release/
docs:
- - title: "快速入门"
+ - title: "基于java微服务SDK开发微服务应用"
url: /cn/docs/quick-start/
- - title: "微服务应用快速开发"
- url: /cn/docs/quick-start-bmi/
- - title: "微服务开发进阶"
- url: /cn/docs/quick-start-advance/
children:
+ - title: "快速入门"
+ url: /cn/docs/quick-start/
+ - title: "体质指数微服务应用快速开发"
+ url: /cn/docs/quick-start-bmi/
+ - title: "微服务开发进阶"
+ url: /cn/docs/quick-start-advance/
- title: "负载均衡"
url: /cn/docs/quick-start-advance/load-balance/
- title: "流量控制"
@@ -135,6 +154,21 @@ t:
url: /cn/docs/quick-start-advance/service-management/
- title: "分布式调用链追踪"
url: /cn/docs/quick-start-advance/distributed-tracing/
+ - title: "使用mersher接入servicecomb微服务体系"
+ url: /cn/docs/mersher-quick-start/
+ children:
+ - title: "快速入门"
+ url: /cn/docs/mersher-quick-start/
+ - title: "mersher进阶"
+ url: /cn/docs/mersher-quick-start-advance/
+ - title: "mersher负载均衡"
+ url: /cn/docs/mersher-quick-start-advance/mersher-load-balance/
+ - title: "mersher流量控制"
+ url: /cn/docs/mersher-quick-start-advance/mersher-flow-control/
+ - title: "mersher服务治理"
+ url: /cn/docs/mersher-quick-start-advance/mersher-service-management/
+ - title: "mersher分布式调用链追踪"
+ url: /cn/docs/mersher-quick-start-advance/mersher-distributed-tracing/
users:
- title: Java Chassis
diff --git a/_docs/cn/mersher-distributed-tracing.md b/_docs/cn/mersher-distributed-tracing.md
new file mode 100644
index 0000000..815b86e
--- /dev/null
+++ b/_docs/cn/mersher-distributed-tracing.md
@@ -0,0 +1,48 @@
+---
+title: 分布式调用链追踪
+lang: cn
+ref: mersher-distributed-tracing
+permalink: /cn/docs/mersher-quick-start-advance/mersher-distributed-tracing/
+excerpt: 介绍如何在体质指数应用中使用ServiceComb提供的分布式追踪能力
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+- 分布式调用链追踪提供追溯微服务调用关系和调用处理时延的能力，便于用户检查分布式环境中微服务的健康状态。本指南将展示如何使用 **mersher** 提供的分布式调用链追踪能力。
+
+# 前言
+
+- 在您进一步阅读之前，请确保您已阅读了[mersher快速入门](/cn/docs/mersher-quick-start/)，并已成功运行用例服务。
+
+# 启用
+
+- 1、mersher main文件中添加对zipkin库依赖：
+
+ ```bash
+ _ "github.com/go-chassis/go-chassis-plugins/tracing/zipkin"
+ ```
+
+- 2、启发器bootstrap.go中添加默认处理函数，如图中箭头所示：
+
+ 
+
+- 3、重新编译，分别替换**mersher-g**、**mersher-a**和**mersher-b**的可执行文件，启动mersher服务；
+
+- 4、使用**Docker**运行[Zipkin分布式追踪服务](http://servicecomb.apache.org/cn/docs/quick-start-advance/distributed-tracing/)
+
+- 5、多次点击 _Submit_ 按钮发起服务调用；
+
+- 6、打开 <http://192.168.88.64:9411>可查看分布式追踪结果如图，可以通过host地址看到分别调用了**mersher-a**(监听30108端口)和**mersher-b**（监听30111端口）：
+
+ <br>
+
+ 
+
+# 下一步
+
+- 了解更多[分布式调用链追踪](/cn/users/distributed-tracing/)
+
+- 阅读[基于 ServiceComb 和 Zipkin 的分布式调用链追踪](/cn/docs/tracing-with-servicecomb/)来进一步了解分布式追踪
+
+- 认识 [**ServiceComb** 微服务开发框架](/cn/users/)
+
+- 通过 [Company应用](/cn/docs/linuxcon-workshop-demo/) 更深入地了解微服务开发
diff --git a/_docs/cn/mersher-flow-control.md b/_docs/cn/mersher-flow-control.md
new file mode 100644
index 0000000..297cc9d
--- /dev/null
+++ b/_docs/cn/mersher-flow-control.md
@@ -0,0 +1,45 @@
+---
+title: 流量控制
+lang: cn
+ref: mersher-flow-control
+permalink: /cn/docs/mersher-quick-start-advance/mersher-flow-control/
+excerpt: 介绍如何在体质指数应用中使用ServiceComb框架提供的流量控制能力
+last_modified_at: 2017-09-03T14:01:43.000Z
+---
+
+- 流量控制通过控制数据传输速率来避免微服务过载运行。本指南将展示如何使用 **mersher** 提供的流量控制能力。
+
+# 前言
+
+- 在您进一步阅读之前，请确保您已阅读了[mersher快速入门](/cn/docs/mersher-quick-start/)，并已成功运行用例服务。
+
+# 开启
+
+- 添加流量控制配置，重启服务，更改**mersher-a**配置文件**chassis.yaml**，其中流量控制包含下列选项：
+
+ ```yaml
+ flowcontrol:
+ Provider:
+ qps:
+ enabled: true # enable rate limiting or not
+ global:
+ limit: 0 # default limit of provider
+ limit:
+ Server: 0 # rate limit for request from a provider
+ ```
+
+ 该频率限制标识每秒接受的请求为0，即不提供服务。
+
+# 验证
+
+- 点击 _Submit_ 按钮，此时能看到由于流控受限而请求被拒的界面，请求已经无法到达httpserver。
+
+ 
+
+ 
+
+# 下一步
+
+- 阅读[服务治理快速入门](/cn/docs/mersher-quick-start-advance/mersher-service-management/)
+
+- 了解更多[流量控制](/cn/users/service-configurations/#限流策略)的使用方式
diff --git a/_docs/cn/mersher-load-balance.md b/_docs/cn/mersher-load-balance.md
new file mode 100644
index 0000000..913fbad
--- /dev/null
+++ b/_docs/cn/mersher-load-balance.md
@@ -0,0 +1,36 @@
+---
+title: 负载均衡
+lang: cn
+ref: mersher-load-balance
+permalink: /cn/docs/mersher-quick-start-advance/mersher-load-balance/
+excerpt: 介绍如何在体质指数应用中使用mersher提供的负载均衡能力
+last_modified_at: 2017-09-03T14:01:43.000Z
+---
+
+- mersher支持灵活的负载均衡算法。本指南将展示如何使用 **mersher** 提供的负载均衡能力。
+
+# 前言
+
+- 在您进一步阅读之前，请确保您已阅读了[mersher快速入门](/cn/docs/mersher-quick-start/)，并已成功运行用例服务。
+
+# 负载均衡算法
+
+- 1、默认情况下会使用roundbin（轮询）负载均衡算法，另外还支持Random和SessionStickiness负载均衡算法。 我们将负载均衡方法配置为Random，修改mersher-g的配置文件chassis.yaml：
+
+ ```bash
+ loadbalance:
+ strategy:
+ name: Random
+ ```
+
+- 2、此时点击 _Submit_ 按钮就可以看到如下两个界面中的BMI Instance ID随机出现。
+
+ <br>
+
+ 
+
+# 下一步
+
+- 阅读[流量控制快速入门](/cn/docs/mersher-quick-start-advance/mersher-flow-control/)
+
+- 了解更多[负载均衡](/cn/users/service-configurations/#负载均衡策略)的使用方式
diff --git a/_docs/cn/mersher-quick-start-advance.md b/_docs/cn/mersher-quick-start-advance.md
new file mode 100644
index 0000000..071da90
--- /dev/null
+++ b/_docs/cn/mersher-quick-start-advance.md
@@ -0,0 +1,24 @@
+---
+title: mersher开发进阶
+lang: cn
+ref: mersher-quick-start-advance
+permalink: /cn/docs/mersher-quick-start-advance/
+excerpt: 介绍如何在体质指数应用中使用ServiceComb的处理链能力
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+本指南将带您进入使用**mersher**接入**ServiceComb**的进阶之旅。在此旅程，您将能学到如何使用**mersher**的微服务高级特性：
+
+- [mersher负载均衡](/cn/docs/mersher-quick-start-advance/mersher-load-balance/)。支持灵活可配置的微服务负载均衡策略。
+
+- [mersher流量控制](/cn/docs/mersher-quick-start-advance/mersher-flow-control/)。支持微服务请求流量控制能力。
+
+- [mersher服务治理](/cn/docs/mersher-quick-start-advance/mersher-service-management/)。支持微服务的灰度发布和熔断等治理能力。
+
+- [mersher分布式追踪](/cn/docs/mersher-quick-start-advance/mersher-distributed-tracing)。支持追溯微服务调用关系链的能力。
+
+# 下一步
+
+- 认识 [**ServiceComb** 微服务开发框架](/cn/users/)
+
+- 通过 [Company应用](/cn/docs/linuxcon-workshop-demo/) 更深入地了解微服务开发
diff --git a/_docs/cn/mersher-quick-start.md b/_docs/cn/mersher-quick-start.md
new file mode 100644
index 0000000..93a9b93
--- /dev/null
+++ b/_docs/cn/mersher-quick-start.md
@@ -0,0 +1,155 @@
+---
+title: mersher快速入门
+lang: cn
+ref: mersher-quick-start
+permalink: /cn/docs/mersher-quick-start/
+excerpt: 介绍如何使用mersher快速改造微服务应用
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+# 安装 Go 和 Python 开发环境
+
+- 安装**git**，详情可参考[git安装教程](https://git-scm.com/book/zh/v2/%E8%B5%B7%E6%AD%A5-%E5%AE%89%E8%A3%85-Git){:target="_blank"}。
+
+- 安装**golang 1.12.7** ，详情可参考[Go安装教程](https://golang.google.cn/doc/install){:target="_blank"}。
+
+- 安装**python 2.7**，详情可参考[python安装教程](https://wiki.python.org/moin/BeginnersGuide/Download){:target="_blank"}。
+
+# 运行 Service Center
+
+在 **ServiceComb** 微服务框架中，**Service Center** 提供服务注册及服务发现功能，可直接使用 Docker 运行。
+
+```bash
+docker pull servicecomb/service-center
+docker run -d -p 30100:30100 servicecomb/service-center:latest
+```
+
+_您可以通过阅读[环境配置](/cn/users/setup-environment/#运行service-center)获取在本地以二进制方式运行**Service Center**和**front**的方法。_
+
+# 使用mersher接入servicecomb微服务体系
+
+## 案例背景
+
+- 本用例主要是帮助用户快速入门**mersher sidecar模式**；希望用户通过该例子，快速上手使用mersher服务，了解mersher的工作模式，并了解如何通过mersher的帮助改造已有的http服务，接入ServiceComb微服务体系，得到go-chassis微服务框架提供的负载均衡、流控、服务治理、调用链追踪等微服务能力。
+
+## 用例服务介绍
+
+- 1、 **httpserver-a**：基于go语言实现的http体质指数服务，可替换为任何语言开发的http服务；
+- 2、 **httpserver-b**：基于python语言实现的http体质指数服务，功能与httpserver-a相同，可替换为任何语言开发的http服务；
+- 3、 **mersher-a**：通过sidecar模式为httpserver-a提供服务的mersher实例；
+- 4、 **mersher-b**：通过sidecar模式为httpserver-b提供服务的mersher实例；
+- 5、 **mersher-g**：通过sidecar模式为httpserver-gateway提供服务的mersher实例；
+- 6、 **servicecenter**：服务中心，接收mesher服务的注册，提供服务发现、路由查询、服务监控功能；
+- 7、 **webapp**：来源于bmi示例，用于在浏览器上展示可视化结果，使用ajax发起http服务调用；
+- 8、 **httpserver-gateway**：内部服务服务统一出口，接收webapp服务请求，作为bmi（体质指数）客户端发起http请求；
+
+ 
+
+## 流程详情
+
+- 1、 浏览器通过 **webapp** 服务发起http调用[]()<http://192.168.88.64:4538/bmi>；
+- 2、 httpserver-gateway服务接收请求，并发起对地址[]()<http://mersher-provider/bmi>的http调用，因为设置了代理[]()<http://127.0.0.1:30101>，**httpserver-gateway** 发起的请求将被转发到 **mersher-g** 服务；
+- 3、 **mersher-g** 根据请求的服务名(microservice.yaml配置的服务名**mersher-provider**）从服务中心**servicecenter**获得该服务名的地址，根据负载均衡算法（默认轮询）转发到部署的两个**mersher**(**mersher-a**和**mersher-b**)之一；
+- 4、 **mersher**(**mersher-a**和**mersher-b**)服务根据设置好的spefic地址，转发到自己绑定的**provider**服务(**httpserver_a**和**httpserver_b**)服务进行处理；
+- 5、 **httpserver_a**和**httpserver_b**会根据用户身高和体重进行计算，并返回自己的服务标识展示在界面上；流程图如下所示：
+
+ 
+
+## 环境搭建
+
+- 1、 编译 **mersher** ：[下载地址](https://github.com/apache/servicecomb-mesher), 按README.md编译项目 得到可执行文件mersher（linux），windows（mersher.exe）；
+- 2、 创建 **mersher-g** 用于接收客户端请求： 在mersher目录下执行下列linux命令创建mersher-g，此处除了可执行文件，还需要拷贝conf
+
+ ```bash
+ mkdir /usr/local/src/mersher-g
+ cp ./mesher /usr/local/src/mersher-g
+ cp -r ./conf /usr/local/src/mersher-g
+ ```
+
+ 更改conf中配置文件，microservice.yaml中的**服务name**，从hellomesher改为**mersher-consumer**；更改chassis.yaml中监听的服务地址，从本地回环（127.0.0.1）地址改为**内网ip**（linux下通过ifconfig查看，如192.168.88.64）:
+
+ ```bash
+ listenAddress: 127.0.0.1:40101 -----》 listenAddress: 192.168.88.64:40101
+ listenAddress: 127.0.0.1:30101 -----》 listenAddress: 192.168.88.64:30101
+ listenAddress: 127.0.0.1:30102 -----》 listenAddress: 192.168.88.64:30102
+ ```
+
+- 3、 创建mersher-a和mersher-b
+
+ ```bash
+ mkdir /usr/local/src/mersher-a
+ cp ./mesher /usr/local/src/mersher-a
+ cp -r ./conf /usr/local/src/mersher-a
+ mkdir /usr/local/src/mersher-b
+ cp ./mesher /usr/local/src/mersher-b
+ cp -r ./conf /usr/local/src/mersher-b
+ ```
+
+ 更改conf中配置文件，分别更改**microservice.yaml**中的**服务name**为相同的**mersher-provider**；<br>
+ 更改**mersher-a**配置**chassis.yaml**监听的地址和端口：
+
+ ```bash
+ listenAddress: 127.0.0.1:40101 -----》 listenAddress: 192.168.88.64:40107
+ listenAddress: 127.0.0.1:30101 -----》 listenAddress: 192.168.88.64:30111
+ listenAddress: 127.0.0.1:30102 -----》 listenAddress: 192.168.88.64:30112
+ ```
+
+ 更改**mersher-b**配置**chassis.yaml**监听的地址和端口：
+
+ ```bash
+ listenAddress: 127.0.0.1:40101 -----》 listenAddress: 192.168.88.64:40102
+ listenAddress: 127.0.0.1:30101 -----》 listenAddress: 192.168.88.64:30108
+ listenAddress: 127.0.0.1:30102 -----》 listenAddress: 192.168.88.64:30109
+ ```
+
+- 4、 启动mersher服务，分别进入mersher-g、mersher-a和mersher-b，启动服务，其中需要设置mersher-a和mersher-b的SPECIFIC_ADDR地址，该地址用于将mersher和http服务绑定起来；
+
+ ```bash
+ cd /usr/local/src/mersher-a
+ export SPECIFIC_ADDR=127.0.0.1:4537
+ ./mersher
+ ```
+
+ ```bash
+ cd /usr/local/src/mersher-b
+ export SPECIFIC_ADDR=127.0.0.1:4540
+ ./mersher
+ ```
+
+ ```bash
+ cd /usr/local/src/mersher-g
+ ./mersher
+ ```
+
+- 5、 搭建**httpserver**作为http provier服务，**httpserver-gateway**作为http client服务：
+
+ ```bash
+ go build httpserver.go
+ ./httpserver.go
+ go build httpservergateway.go
+ ./httpservergateway
+ ```
+
+- 6、运行**http_server.py**程序，需要安装python2.7，依赖BaseHTTPServer包；
+
+- 7、 使用[**Bmi体质指数**](/cn/docs/quick-start.md/) 中的webapp作为展示服务，将webapp/src/main/resources/static/index.html 静态页面中 ajax调用的地址从/calculator/bmi?height=改为[]()<http://192.168.88.64:4538/bmi?height=> 这个地址是httpservergateway客户端服务的监听地址；
+
+## 开始测试
+
+- 1、 浏览器打开页面<http://192.168.88.64:30103> (如果打不开需要开启服务中心service-center的front服务，参考 <<http://servicecomb.apache.org/cn/users/setup-environment/#%E8%BF%90%E8%A1%8Cservice-center>) 查看服务，可以看到如下界面。其中gateway是上述的webapp服务，这里展示的是microservice.yaml中配置的服务名。大写的SERVICECENTER是服务中心；
+
+ 
+
+- 2、 浏览器打开<http://192.168.88.64:8889>，可以看到如下界面，为webapp呈现的静态页面：
+
+ 
+
+- 3、 输入参数(180、70)点击submit，观察BMI Instance ID变化：
+
+ <br>
+
+ 
+
+# 下一步
+
+- 阅读[**mersher**进阶](/cn/docs/mersher-quick-start-advance.md/)。
diff --git a/_docs/cn/mersher-service-management.md b/_docs/cn/mersher-service-management.md
new file mode 100644
index 0000000..55fcfef
--- /dev/null
+++ b/_docs/cn/mersher-service-management.md
@@ -0,0 +1,87 @@
+---
+title: 服务治理
+lang: cn
+ref: mersher-service-management
+permalink: /cn/docs/mersher-quick-start-advance/mersher-service-management/
+excerpt: 介绍如何在体质指数应用中使用ServiceComb提供的服务治理能力
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+- 服务治理主要用于对分布式系统中大量微服务进行有效控制管理。本指南将会展示如何使用 **mersher** 提供的服务治理能力。
+
+# 前言
+
+- 在您进一步阅读之前，请确保您已阅读了[mersher快速入门](/cn/docs/mersher-quick-start/)，并已成功运行mersher用例服务。
+
+# 灰度发布
+
+## 配置
+
+- 1、更新版本号： 分别更改**mersher-a**和**mersher-b**的配置文件**microservice.yaml**，更新**version**字段分别为**1.1.1**和**1.1.2**，重启mersher服务，可以看到服务版本号发生了变更。如图中所示：
+
+ 
+
+- 2、配置路由信息，更改mersher-g的配置文件router.yaml，按实例版本更新权重信息，并重启服务：
+
+ ```yaml
+ routeRule:
+ mersher-provider: #service name
+ - precedence: 2 #precedence of route rule
+ route: #route rule list
+ - tags:
+ version: 1.1.1
+ weight: 80 #weight of 20%
+ - tags:
+ version: 1.1.2
+ weight: 20 #weight of 20%
+ ```
+
+## 验证
+
+- 此时大量点击 _Submit_ 按钮就可以看到BMI Instance ID按配置的比例交替出现。
+
+# 服务熔断及恢复
+
+## 配置
+
+- 更改断流器配置，更改mersher-g的配置文件chassis.yaml，设置其中的断流器配置为：
+
+ ```yaml
+ isolation:
+ Consumer:
+ timeout:
+ enabled: true
+ timeoutInMilliseconds: 1000 #超时时间
+ maxConcurrentRequests: 1
+ circuitBreaker:
+ Consumer:
+ enabled: true
+ forceOpen: false
+ forceClosed: false
+ sleepWindowInMilliseconds: 10000 #熔断恢复时间10秒
+ requestVolumeThreshold: 1 #请求量限制
+ errorThresholdPercentage: 1
+ fallback:
+ Consumer:
+ enabled: true
+ maxConcurrentRequests: 1
+ fallbackpolicy:
+ Consumer:
+ policy: returnnull
+ ```
+
+## 验证
+
+- 1、传入负数参数，响应超时，mersher-g断流器生效 mersher-service-management-circuitbreaker
+
+ 
+
+ 
+
+- 2、根据配置参数sleepWindowInMilliseconds，过10秒后服务自动恢复
+
+# 下一步
+
+- 阅读[分布式追踪快速入门指南](/cn/docs/mersher-quick-start-advance/mersher-distributed-tracing/)
+
+- 了解更多[服务治理](/cn/users/service-configurations/)的使用方式
diff --git a/_docs/mersher-distributed-tracing.md b/_docs/mersher-distributed-tracing.md
new file mode 100644
index 0000000..c02b1ef
--- /dev/null
+++ b/_docs/mersher-distributed-tracing.md
@@ -0,0 +1,54 @@
+---
+title: Mersher Distributed Tracing
+lang: en
+ref: mersher-distributed-tracing
+permalink: /docs/mersher-quick-start-advance/mersher-distributed-tracing/
+excerpt: Introduce how to use distributed tracing with mersher
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+- Distributed handler chain tracking provides the ability of tracing microservice call relationships and watching delays of calling processing. It is used to make it easy for users to check the health of microservices in a distributed environment. This guide will show you how to use the distributed handler chain tracking capabilities provided by **mersher**.
+
+# Foreword
+
+- Walk through [mersher-quick-start](/docs/mersher-quick-start/) and have **mersher display programs** running.
+
+# Enable
+
+- 1 Added zipkin library dependency in mersher main file.
+
+ ```bash
+ _ "github.com/go-chassis/go-chassis-plugins/tracing/zipkin"
+ ```
+
+- 2 Add default handlers in bootstrap.go as shown by the arrows in the figure.
+
+ 
+
+- 3 Recompile and replace the executables of **mersher-g**,**mersher-a** and **mersher-b**.Then start the mersher service respectively.
+
+- 4 Running Zipkin Distributed tracking service with docker.
+
+ ```bash
+ docker run -d -p 9411:9411 openzipkin/zipkin
+ ```
+
+- 5 Multiple clicks on the _Submit_ button to initiate multiple service calls.
+
+- 6 Open <http://192.168.88.64:9411> to view the distributed tracking results. You can see the call chains and call delays of **mersher-a** (listening port 30108) and **mersher-b** (listening port 30111).
+
+ <br>
+
+ 
+
+# What's next
+
+- Learn more about [Distributed Tracing](/users/distributed-tracing/)
+
+- Read [Distributed Tracing with ServiceComb and Zipkin](/docs/tracing-with-servicecomb/)
+
+- See [ServiceComb User Guide](/users/)
+
+- Learn more from [the Company application](/docs/linuxcon-workshop-demo/) for a more complete example of microservice applications integrated with ServiceComb
+
+ ``
diff --git a/_docs/mersher-flow-control.md b/_docs/mersher-flow-control.md
new file mode 100644
index 0000000..1e2a613
--- /dev/null
+++ b/_docs/mersher-flow-control.md
@@ -0,0 +1,45 @@
+---
+title: Mersher Flow Control
+lang: en
+ref: mersher-flow-control
+permalink: /docs/mersher-quick-start-advance/mersher-flow-control/
+excerpt: Describe how to use the flow control capabilities provided by mersher
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+- Flow control avoids microservice overload operations by controlling the data transfer rate. This guide will show you how to use the flow control capabilities provided by **mersher**
+
+# Before you start
+
+- Walk through [mersher-quick-start](/docs/mersher-quick-start/) and have **mersher display programs** running.
+
+# Enable
+
+- Change the **mersher-a's** configuration file **chassis.yaml**. Add a flow control configuration in **chassis.yaml** as follows. Restart the service.
+
+ ```yaml
+ flowcontrol:
+ Provider:
+ qps:
+ enabled: true # enable rate limiting or not
+ global:
+ limit: 0 # default limit of provider
+ limit:
+ Server: 0 # rate limit for request from a provider
+ ```
+
+ The frequency limit configuration make the request accepted per second is 0 which means no service is provided.
+
+# Verification
+
+- Click the _Submit_ button and you can see that the request was rejected due to the flow control of mersher. Now the request can't reach real httpserver.
+
+
+
+
+
+# What's next
+
+- See quick start for [Service Management](/docs/mersher-quick-start-advance/mersher-service-management/)
+
+- Learn more about [Flow Control](/users/service-configurations/#限流策略)
diff --git a/_docs/mersher-load-balance.md b/_docs/mersher-load-balance.md
new file mode 100644
index 0000000..97f1fb2
--- /dev/null
+++ b/_docs/mersher-load-balance.md
@@ -0,0 +1,38 @@
+---
+title: Mersher Load Balance
+lang: en
+ref: mersher-load-balance
+permalink: /docs/mersher-quick-start-advance/mersher-load-balance/
+excerpt: Describe how to use the load balancing capabilities provided by Mersher
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+- Mersher supports flexible load balancing algorithms. This guide will show you how to use the load balancing capabilities provided by **mersher**.
+
+# Foreword
+
+- Walk through [mersher-quick-start](/docs/mersher-quick-start/) and have **mersher display programs** running.
+
+# Enable
+
+- The **Roundbin** load balancing algorithm is used by default and the **Random**, SessionStickiness load balancing algorithms are also supported. We configure the load balancing method **Random** by modifing **mersher-g's** configuration file chassis.yaml.
+
+ ```yaml
+ loadbalance:
+ strategy:
+ name: Random
+ ```
+
+# Verification
+
+- Multiple clicks the _Submit_ button and we can see that the BMI Instance ID in the following two interfaces appear randomly.
+
+ <br>
+
+ 
+
+## What's next
+
+- See quick start for [Flow Control](/docs/mersher-quick-start-advance/mersher-flow-control/)
+
+- Learn more about [Load Balance](/users/service-configurations/#负载均衡策略)
diff --git a/_docs/mersher-quick-start-advance.md b/_docs/mersher-quick-start-advance.md
new file mode 100644
index 0000000..b0e99f6
--- /dev/null
+++ b/_docs/mersher-quick-start-advance.md
@@ -0,0 +1,24 @@
+---
+title: Mersher Development Advanced
+lang: en
+ref: mersher-quick-start-advance
+permalink: /docs/mersher-quick-start-advance/
+excerpt: Describe how to use mersher's advanced microservice capabilities
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+This guide will show you how to use the advanced features of **mersher** to support the microservices system better.
+
+- [mersher for load balance](/docs/mersher-quick-start-advance/mersher-load-balance/) Support for flexible and configurable microservice load balancing strategies.
+
+- [mersher for flow control](/docs/mersher-quick-start-advance/mersher-flow-control/) Support microservice request flow control capabilities.
+
+- [mersher for service management](/docs/mersher-quick-start-advance/mersher-service-management/) Supports micro-service grayscale publishing, service fusing and other management capabilities.
+
+- [mersher for distributed tracing](/docs/mersher-quick-start-advance/mersher-distributed-tracing) Supports the ability to track the chain of call relationships of microservices.
+
+# What's next
+
+- See [ServiceComb User Guide](/users/)
+
+- Learn more from [the Company application](/docs/linuxcon-workshop-demo/) for a more complete example of microservice applications integrated with ServiceComb
diff --git a/_docs/mersher-quick-start.md b/_docs/mersher-quick-start.md
new file mode 100644
index 0000000..fcbaa5a
--- /dev/null
+++ b/_docs/mersher-quick-start.md
@@ -0,0 +1,155 @@
+---
+title: Mersher Quick Start
+lang: en
+ref: mersher-quick-start
+permalink: /docs/mersher-quick-start/
+excerpt: Describe how to use mersher to merge into the servicecomb microservice system
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+# Install Go and Python development environment
+
+- Install **git**. Get details [git Installation tutorial](https://git-scm.com/book/zh/v2/%E8%B5%B7%E6%AD%A5-%E5%AE%89%E8%A3%85-Git){:target="_blank"}.
+
+- Install **golang 1.12.7**. Get details [Go Installation tutorial](https://golang.google.cn/doc/install){:target="_blank"}.
+
+- Install **python 2.7**. Get details [python Installation tutorial](https://wiki.python.org/moin/BeginnersGuide/Download){:target="_blank"}。
+
+# Run Service Center
+
+In the **ServiceComb** microservices framework, **Service Center** provides service registration and service discovery, which can be run directly using Docker.
+
+```bash
+docker pull servicecomb/service-center
+docker run -d -p 30100:30100 servicecomb/service-center:latest
+```
+
+_Reference to [service center deployment](/users/setup-environment/#运行service-center) to learn deploying Service Center and front as a local binary._
+
+# Use mersher to merge into the servicecomb microservice system
+
+## Background
+
+- This use case is mainly to help users get started quickly with **mersher sidecar mode**. We hope that users can understand the working mode of mersher and learn how to merge the existing http service into the ServiceComb micro-service system with mersher's help. The final goal is to help user get the micro-service capabilities such as load balancing, flow control, service management and call chain tracing provided by servicecomb.
+
+## Mersher use case service introduction
+
+- 1 **httpserver-a**: A http server based on golang which is for BMI calculator and can be developed by any language.
+- 2 **httpserver-b**: A http server based on python which is for BMI calculator and can be developed by any language.
+- 3 **mersher-a**: A mersher instance which serves for httpserver-a via sidecar mode.
+- 4 **mersher-b**: A mersher instance which serves for httpserver-b via sidecar mode.
+- 5 **mersher-g**: A mersher instance which serves for httpserver-gateway via sidecar mode.
+- 6 **servicecenter**: Servicecenter which receives registration of mesher service and provides services as service discovery, routing query, service monitoring and so on.
+- 7 **webapp**: A http server which reuses the bmi example service is used for displaying visual results on the browser and using ajax to execute http service calls.
+- 8 **httpserver-gateway**: A http server which is used as an unified export of internal services receives webapp's requestand and then execute HTTP request as a BMI client.
+
+ 
+
+## Process details
+
+- 1 The browser execute a http call via the **webapp** service []()<http://192.168.88.64:4538/bmi>.
+- 2 The httpserver-gateway service receives the request and execute http call []()<http://mersher-provider/bmi>. Because the proxy is set as []()<http://127.0.0.1:30101>, the request initiated by **httpserver-gateway** will be forwarded to the **mersher-g** service.
+- 3 **mersher-g** gets the address of the service name from the **servicecenter** based on the requested service name(the service name **mersher-provider** here is configured in microservice.yaml) and forwarded to one of the two **mersher** (**mersher-a** and **mersher-b**) according to the load balancing algorithm (default polling);
+- 4 **mersher** (**mersher-a** and **mersher-b**) services forward http requests to their own **provider** service (**httpserver_a** or **httpserver_b**) based on the spefic address.
+- 5 **httpserver_a** and **httpserver_b** will calculate according to the user's height and weight, and return their own service ID displayed on the interface. The flow chart is as follows:
+
+ 
+
+## Environmental construction
+
+- 1 Compile **mersher** in [download](https://github.com/apache/servicecomb-mesher). Download the project by README.md to get the executable mersher(linux) or mersher.exe(windows).
+- 2 Create **mersher-g** to receive client requests. In the mersher directory execute the following linux command to create mersher-g. In order to the execute mersher you also need to copy the conf.
+
+ ```bash
+ mkdir /usr/local/src/mersher-g
+ cp ./mesher /usr/local/src/mersher-g
+ cp -r ./conf /usr/local/src/mersher-g
+ ```
+
+ Change **service name** in microservice.yaml from hellemesher to **mersher-consumer**. Change the listening service address in chassis.yaml from 127.0.0.1 to **intranet ip**（Viewed by cmd ifconfig in linux, such as 192.168.88.64）:
+
+ ```bash
+ listenAddress: 127.0.0.1:40101 -----》 listenAddress: 192.168.88.64:40101
+ listenAddress: 127.0.0.1:30101 -----》 listenAddress: 192.168.88.64:30101
+ listenAddress: 127.0.0.1:30102 -----》 listenAddress: 192.168.88.64:30102
+ ```
+
+- 3 Create mersher-a and mersher-b services.
+
+ ```bash
+ mkdir /usr/local/src/mersher-a
+ cp ./mesher /usr/local/src/mersher-a
+ cp -r ./conf /usr/local/src/mersher-a
+ mkdir /usr/local/src/mersher-b
+ cp ./mesher /usr/local/src/mersher-b
+ cp -r ./conf /usr/local/src/mersher-b
+ ```
+
+ Change the **service name** in **microservice.yaml** from hellemesher to **mersher-provider** for both mersher-a and mersher-b<br>
+ Change the listening address and port set in the **mersher-a** configuration file **chassis.yaml**:
+
+ ```bash
+ listenAddress: 127.0.0.1:40101 -----》 listenAddress: 192.168.88.64:40107
+ listenAddress: 127.0.0.1:30101 -----》 listenAddress: 192.168.88.64:30111
+ listenAddress: 127.0.0.1:30102 -----》 listenAddress: 192.168.88.64:30112
+ ```
+
+ Change the listening address and port set in the **mersher-b** configuration file **chassis.yaml**:
+
+ ```bash
+ listenAddress: 127.0.0.1:40101 -----》 listenAddress: 192.168.88.64:40102
+ listenAddress: 127.0.0.1:30101 -----》 listenAddress: 192.168.88.64:30108
+ listenAddress: 127.0.0.1:30102 -----》 listenAddress: 192.168.88.64:30109
+ ```
+
+- 4 Start running mersher-g, mersher-a and mersher-b respectively by cmd.
+
+```bash
+cd /usr/local/src/mersher-a
+export SPECIFIC_ADDR=127.0.0.1:4537
+./mersher
+```
+
+```bash
+cd /usr/local/src/mersher-b
+export SPECIFIC_ADDR=127.0.0.1:4540
+./mersher
+```
+
+```bash
+cd /usr/local/src/mersher-g
+./mersher
+```
+
+- 5 Use **httpserver** to provide http service. Use **httpserver-gateway** as the client to execute http request to **httpserver**.
+
+ ```bash
+ go build httpserver.go
+ ./httpserver.go
+ go build httpservergateway.go
+ ./httpservergateway
+ ```
+
+- 6 Run **http_server.py** program. You need to install python2.7 and this service relies on BaseHTTPServer package.
+
+- 7 Use webapp as a user interface which is in [**Bmi-example**](/docs/quick-start.md/). Edit http address of the ajax call from /calculator/bmi?height= to []()<http://192.168.88.64:4538/bmi?height=> in static page webapp/src/main/resources/static/index.html. This address is the listening address of the httpservergateway.
+
+## Start testing
+
+- 1 Open url <http://192.168.88.64:30103> in browser. (If you can't open it, you need to open the front service of the service-center. Referring <http://servicecomb.apache.org/users/setup-environment/#%E8%BF%90%E8%A1%8Cservice-center>). You can see services information in web. The name 'gateway' represents the webapp service introduced above which is the service name configured in microservice.yaml. SERVICECENTER represents the servicecenter.
+
+ 
+
+- 2 Open <http://192.168.88.64:8889> in browser and you can see the following interface.
+
+ 
+
+- 3 Enter the parameters (180, 70) and click submit to observe change of the BMI Instance ID.
+
+ <br>
+
+ 
+
+# What's next
+
+- Read [**mersher** quick start advance](/docs/mersher-quick-start-advance.md/)
diff --git a/_docs/mersher-service-management.md b/_docs/mersher-service-management.md
new file mode 100644
index 0000000..3b437ce
--- /dev/null
+++ b/_docs/mersher-service-management.md
@@ -0,0 +1,87 @@
+---
+title: Mersher Service Management
+lang: en
+ref: mersher-service-management
+permalink: /docs/mersher-quick-start-advance/mersher-service-management/
+excerpt: Describe how to use the service management capabilities provided by mersher
+last_modified_at: 2019-08-08T14:01:43.000Z
+---
+
+- Service management is mainly used to effectively control and manage a large number of microservices in distributed systems. This guide will show you how to use the service management capabilities provided by **mersher**.
+
+# Before you start
+
+- Walk through [mersher-quick-start](/docs/mersher-quick-start/) and have **mersher display programs** running.
+
+# Grayscale release
+
+## Configuration
+
+- 1、Change the version number respectively in conf **microservice.yaml** of **mersher-a** and **mersher-b**. Change the **version** field to **1.1.1** and **1.1.2** respectively.Restart the mersher service and you can see that the service version number has changed in servicecenter.
+
+ 
+
+- 2、Change weight options in configuration files router.yaml of mersher-g. Then restart service.
+
+ ```yaml
+ routeRule:
+ mersher-provider: #service name
+ - precedence: 2 #precedence of route rule
+ route: #route rule list
+ - tags:
+ version: 1.1.1
+ weight: 80 #weight of 80%
+ - tags:
+ version: 1.1.2
+ weight: 20 #weight of 20%
+ ```
+
+## Verification
+
+- Click the _Submit_ button repeatedly and you can see that the BMI Instance ID keep changing according to the weight configuration.
+
+# Circuit breaker
+
+## Configuration
+
+- Change the circuit breaker configuration in chassis.yaml of mersher-g.
+
+ ```yaml
+ isolation:
+ Consumer:
+ timeout:
+ enabled: true
+ timeoutInMilliseconds: 1000
+ maxConcurrentRequests: 1
+ circuitBreaker:
+ Consumer:
+ enabled: true
+ forceOpen: false
+ forceClosed: false
+ sleepWindowInMilliseconds: 10000
+ requestVolumeThreshold: 1
+ errorThresholdPercentage: 1
+ fallback:
+ Consumer:
+ enabled: true
+ maxConcurrentRequests: 1
+ fallbackpolicy:
+ Consumer:
+ policy: returnnull
+ ```
+
+## Verification
+
+- 1 The circuit breaker of mersher-g takes effect when a negative parameter is passed in.
+
+ 
+
+ 
+
+- 2 The service is automatically restored after 10 seconds because of the configuration parameter 'sleepWindowInMilliseconds' take effect.
+
+# What's next
+
+- Read[mersher distributed tracing](/docs/mersher-quick-start-advance/mersher-distributed-tracing/)
+
+- More about [service management](/users/service-configurations/)
diff --git a/assets/images/mersher/mersher-circuitbreaker-ret.png b/assets/images/mersher/mersher-circuitbreaker-ret.png
new file mode 100644
index 0000000..803de40
Binary files /dev/null and b/assets/images/mersher/mersher-circuitbreaker-ret.png differ
diff --git a/assets/images/mersher/mersher-circuitbreaker.png b/assets/images/mersher/mersher-circuitbreaker.png
new file mode 100644
index 0000000..907ae18
Binary files /dev/null and b/assets/images/mersher/mersher-circuitbreaker.png differ
diff --git a/assets/images/mersher/mersher-deployment.png b/assets/images/mersher/mersher-deployment.png
new file mode 100644
index 0000000..ba9c74d
Binary files /dev/null and b/assets/images/mersher/mersher-deployment.png differ
diff --git a/assets/images/mersher/mersher-flow-control-fail.png b/assets/images/mersher/mersher-flow-control-fail.png
new file mode 100644
index 0000000..bab78f0
Binary files /dev/null and b/assets/images/mersher/mersher-flow-control-fail.png differ
diff --git a/assets/images/mersher/mersher-flow-control-log.png b/assets/images/mersher/mersher-flow-control-log.png
new file mode 100644
index 0000000..7b63e68
Binary files /dev/null and b/assets/images/mersher/mersher-flow-control-log.png differ
diff --git a/assets/images/mersher/mersher-flowchart.png b/assets/images/mersher/mersher-flowchart.png
new file mode 100644
index 0000000..569eb6a
Binary files /dev/null and b/assets/images/mersher/mersher-flowchart.png differ
diff --git a/assets/images/mersher/mersher-intro.png b/assets/images/mersher/mersher-intro.png
new file mode 100644
index 0000000..5119f70
Binary files /dev/null and b/assets/images/mersher/mersher-intro.png differ
diff --git a/assets/images/mersher/mersher-ser-manage-ver.png b/assets/images/mersher/mersher-ser-manage-ver.png
new file mode 100644
index 0000000..c65ee50
Binary files /dev/null and b/assets/images/mersher/mersher-ser-manage-ver.png differ
diff --git a/assets/images/mersher/mersher-servercenter.png b/assets/images/mersher/mersher-servercenter.png
new file mode 100644
index 0000000..5279def
Binary files /dev/null and b/assets/images/mersher/mersher-servercenter.png differ
diff --git a/assets/images/mersher/mersher-testgohttp.png b/assets/images/mersher/mersher-testgohttp.png
new file mode 100644
index 0000000..f38f762
Binary files /dev/null and b/assets/images/mersher/mersher-testgohttp.png differ
diff --git a/assets/images/mersher/mersher-testinit.png b/assets/images/mersher/mersher-testinit.png
new file mode 100644
index 0000000..2ed1b64
Binary files /dev/null and b/assets/images/mersher/mersher-testinit.png differ
diff --git a/assets/images/mersher/mersher-testpythonhttp.png b/assets/images/mersher/mersher-testpythonhttp.png
new file mode 100644
index 0000000..7ae96ad
Binary files /dev/null and b/assets/images/mersher/mersher-testpythonhttp.png differ
diff --git a/assets/images/mersher/mersher-tracing-30108.png b/assets/images/mersher/mersher-tracing-30108.png
new file mode 100644
index 0000000..96a55d3
Binary files /dev/null and b/assets/images/mersher/mersher-tracing-30108.png differ
diff --git a/assets/images/mersher/mersher-tracing-30111.png b/assets/images/mersher/mersher-tracing-30111.png
new file mode 100644
index 0000000..4eb5c5a
Binary files /dev/null and b/assets/images/mersher/mersher-tracing-30111.png differ
diff --git a/assets/images/mersher/mersher-tracing-func.png b/assets/images/mersher/mersher-tracing-func.png
new file mode 100644
index 0000000..600f839
Binary files /dev/null and b/assets/images/mersher/mersher-tracing-func.png differ