You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shenyu.apache.org by xi...@apache.org on 2022/05/04 15:26:32 UTC
[incubator-shenyu-website] branch main updated: [#ISSUE 471] divide plugin (#554)
This is an automated email from the ASF dual-hosted git repository.
xiaoyu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-shenyu-website.git
The following commit(s) were added to refs/heads/main by this push:
new de8fecfbed [#ISSUE 471] divide plugin (#554)
de8fecfbed is described below
commit de8fecfbed429bdb40214bfc87caae7b2249c4f4
Author: AhahaGe <ah...@163.com>
AuthorDate: Wed May 4 23:26:28 2022 +0800
[#ISSUE 471] divide plugin (#554)
* divide 插件中文版
* divide 插件中文版
* divide en version
* divide en version and old cn and en versions
---
docs/plugin-center/proxy/divide-plugin.md | 170 +++++++++++++-------
.../version-2.3.0/plugins/divide-plugin.md | 177 +++++++++++++++------
.../plugin-center/http-handle/divide-plugin.md | 165 +++++++++++++------
.../plugin-center/proxy/divide-plugin.md | 161 +++++++++++++------
.../plugin-center/proxy/divide-plugin.md | 161 +++++++++++++------
.../plugin-center/proxy/divide-plugin.md | 169 +++++++++++++-------
.../version-2.3.0/plugins/divide-plugin.md | 163 +++++++++++++++----
.../plugin-center/http-handle/divide-plugin.md | 152 ++++++++++++------
.../plugin-center/proxy/divide-plugin.md | 152 ++++++++++++------
.../plugin-center/proxy/divide-plugin.md | 152 ++++++++++++------
.../plugin-center/proxy/divide-plugin.md | 170 +++++++++++++-------
11 files changed, 1261 insertions(+), 531 deletions(-)
diff --git a/docs/plugin-center/proxy/divide-plugin.md b/docs/plugin-center/proxy/divide-plugin.md
index 16a79ad237..bcf2866071 100644
--- a/docs/plugin-center/proxy/divide-plugin.md
+++ b/docs/plugin-center/proxy/divide-plugin.md
@@ -4,86 +4,142 @@ keywords: ["divide"]
description: divide plugin
---
-## Explanation
+# 1. Overview
-* `Divide` is the core processing plugin for gateway to process `http` requests.
+## 1.1 Plugin Name
-## Plugin Setting
+* `divide` Plugin
-* Add related dependencies and enable plugin, please refer to: [Quick start with Http](../../quick-start/quick-start-http)
+## 1.2 Appropriate Scenario
-* `Http` client access, please refer to：[Http proxy](../../user-guide/http-proxy) .
+* Handling `http protocol` requests.
+* Support traffic management, such as a/b test, grayscale test.
+* Service Load Balancing.
+* Set request timeout.
-## Plugin detail
+## 1.3 Plugin functionality
-The `divide` plugin is a plugin for forward proxying of `http`. All requests of the `http` type are called by the plugin for load balancing.
+* Supports traffic management based on request information such as uri, header, and query.
+* Supports setting the load balancing strategy for requests, and supports service warm-up. Currently, three strategies are supported: ip hash (consistent hash with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Supports setting the maximum value of the request header, the maximum value of the request body, and the request level timeout.
+* Supports setting the timeout retry policy and the number of retries. Currently, the retry policy supports: current (retrying the server that failed before) and failover (retrying other servers).
-<img src="/img/shenyu/plugin/divide/plugin-en.png" width="80%" height="80%" />
+## 1.4 Plugin Code
+* Core module is ```shenyu-plugin-divide```.
+* Core class is ```org.apache.shenyu.plugin.divide.DividePlugin```.
-After the client connects to the `Apache ShenYu` gateway, it will automatically register the selector and rule information. For the selector and rule configuration, please refer to:[Selector And Rule](../../user-guide/admin-usage/selector-and-rule)。
+# 2. How to use plugin
+## 2.1 Plugin-use procedure chart
-#### Selector Handler
+
-<img src="/img/shenyu/plugin/divide/selector_en.png" width="80%" height="80%" />
+## 2.2 Import pom
+- Import maven in shenyu-bootstrap project's `pom.xml` file.
-Selector Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , it is the `http` configuration that is actually called after the gateway matches the traffic. You can configure multiple and set the load The balance weight, the specific load balancing strategy, is specified in the rules. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
-* detailed processing setting：
+## 2.3 Enable plugin
- * `host`: input `localhost`,this field is ignored.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status enable.
- * `ip:port`: ip and port, input your true service `ip` + port here.
+
- * `protocol`: `HTTP` protocol, input `http://` or `https://`, default is:`http://` .
+## 2.4 Config plugin
- * `startupTime`: enabling the time.
+### 2.4.1 Configure access parameters in the client project configuration file
- * `weight`: load balancing weight.
+* Client access method and server address. The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+* Client configuration, including the protocol name and the routing address of the service, please use the http protocol here, and the value of contextPath must be configured as the routing address of each service.
- * `warmupTime`: warm-up time.
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http protocol
+ props:
+ contextPath: /http # routing address for each service
+```
+
+### 2.4.2 Configure upstream validity detection parameters in the shenyu-admin configuration file
+
+The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+> Only http-type registries support upstream detection.
- * `status`: open or closed.
+```yaml
+ shenyu:
+ register:
+ registerType: http # Only http-type register center support upstream detection.
+ serverLists:
+ props:
+ checked: true # The default is true, set to false, do not detect.
+ zombieCheckTimes: 5 # The maximum number of zombie upstream detections. If it exceeds 5 times, its validity will no longer be detected. The default value is 5.
+ scheduledTime: 10 # Timing detection interval, the default is 10 seconds.
+ zombieRemovalTimes: 60 # How many seconds the upstream is offline to be considered as a zombie upstream, the default is 60 seconds.
+```
- * `ip + port` check
+### 2.4.3 Configure the selector and rule information of the divide plugin in shenyu-admin
- * there will be a scheduled task in `shenyu-admin` to scan the configured `ip` port, if it is found offline, choose to delete the `ip + port`.
+After the client is started, the [selector and rule](../../user-guide/admin-usage/selector-and-rule) information will be automatically registered in shenyu-admin -> Plugin List -> Proxy -> Divide.
- * can be configured as follows:
+
-```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # default is true, set to false, no detection
- zombieCheckTimes: 5
- scheduledTime: 10 # timing detection interval, the default is 10 seconds
-
- ```
-
-#### Rule Handler
-
- <img src="/img/shenyu/plugin/divide/rule_en.png" width="80%" height="80%" />
-
-Rule Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule). It is the processing rule that the gateway adopts after the final matching of the traffic is completed. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
-
-* detailed processing setting：
- * `loadStrategy`: if the `http` client is a cluster, which load balancing strategy is adopted when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
- * `retryCount`: number of retries for calling the `http` client.
- * `timeout`: timeout period for calling the `http` client.
- * `headerMaxSize`: maximum value of the requested `header`.
- * `requestMaxSize`: maximum size of the request body.
- * `retryStrategy`: supported since `2.4.3`, the retry strategy `after failure`, the default `current` remains compatible with lower versions.
-
- For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`.
-
- Using the `current` policy will continue to retry the call to `http:localhost:1111`;
-
- Using the `failover` policy will retry the call to other services such as `http:localhost:1112` through the `loadStrategy`, if it fails again at this time , call to `http:localhost:1113` until no service is available.
-
\ No newline at end of file
+#### 2.4.3.1 Selector configuration
+
+Example of divide selector. For general selector configuration, please refer to [Selectors and Rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.1.1 Selector handling information configuration
+
+- `host`: fill in `localhost`, this field is not used currently.
+- `ip:port`: `ip` and port, fill in the `ip` + port of your real service here.
+- `protocol`: `http` protocol, fill in `http:` or `https:`, if not fill in, the default is: `http:`.
+- `startupTime`: Startup time in milliseconds.
+- `weight`: load balancing weight, the default value of service startup automatic registration is 50.
+- `warmupTime`: Warmup time, in milliseconds. The server during warmup will calculate the instantaneous weight, and the calculated value will be smaller than the actual configured weight to protect the server just started. The default value of service startup registration is 10. For example, the warm-up time is 100 milliseconds, the current startup is 50 milliseconds, the configured weight is 50, and the actual weight is 25.
+- `status`: On or off, this selector is valid only in the on state.
+
+#### 2.4.3.2 Processing information configuration of rules
+
+Example of divide rule. For general rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.2.1 Rule processing information configuration
+
+- `loadStrategy`: If the `http` client is a cluster, which load balancing strategy is used when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
+- `timeout`: The timeout for calling the `http` client.
+- `retry Count`: The number of retries that failed to call the `http` client timeout.
+- `headerMaxSize`: The maximum value of the requested `header`.
+- `requestMaxSize`: The maximum value of the request body.
+- `retryStrategy`: Supported since `2.4.3`, retry strategy after failure, default `current` to maintain compatibility with lower versions. For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`. Using the `current` strategy will continue to retry calling `http:localhost:1111`; using the `failover` strategy will retry calling other services such as `ht [...]
+
+## 2.5 Examples
+
+### 2.5.1 Example A/B Test
+
+To be added, welcome contribute.
+
+### 2.5.2 Example Grayscale Test
+
+To be added, welcome contribute.
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status disable.
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0/plugins/divide-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0/plugins/divide-plugin.md
index 97232ffb78..3c8a056d28 100755
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0/plugins/divide-plugin.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.3.0/plugins/divide-plugin.md
@@ -5,56 +5,143 @@ keywords: ["divide"]
description: divide插件
---
-## 说明
+# 1. 概述
-* divide插件是网关处理 `http协议`请求的核心处理插件。
+## 1.1 插件名称
-## 插件设置
+* `divide`插件
-* 开启插件，`soul-admin` --> 插件管理--> `divide` 设置为启用。
-* divide插件，配合如下 starter一起才能生效，具体请看：[http用户](../users-guide/http-proxy)。
+## 1.2 适用场景
-```xml
- <!--if you use http proxy start this-->
- <dependency>
- <groupId>org.dromara</groupId>
- <artifactId>soul-spring-boot-starter-plugin-divide</artifactId>
- <version>${last.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.dromara</groupId>
- <artifactId>soul-spring-boot-starter-plugin-httpclient</artifactId>
- <version>${last.version}</version>
- </dependency>
+* 处理 `http协议` 请求
+* 支持流量治理，例如a/b 测试、灰度测试
+* 服务负载均衡
+* 设置接口的超时时间
+
+## 1.3 插件功能
+
+* 支持根据 uri、header、query 等请求信息做流量的治理
+* 支持设置请求的负载均衡策略，同时支持服务预热，目前支持三种策略：ip hash（带虚拟节点的一致性哈希）、round-robbin（加权轮询）、random（加权随机）
+* 支持设置接口级别请求头最大值、请求体最大值、请求超时时间
+* 支持设置超时重试策略和重试次数，目前重试策略支持：current（重试之前失败的服务器）和failover（重试其它服务器）
+
+## 1.4 插件代码
+
+* 核心模块 ```shenyu-plugin-divide```
+* 核心类 ```org.apache.shenyu.plugin.divide.DividePlugin```
+
+# 2. 如何使用插件
+## 2.1 插件使用流程图
+
+
+
+## 2.2 导入 pom
+
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置。
+
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
```
-## 插件讲解
-
-* divide插件是进行http正向代理的插件，所有http类型的请求，都是由该插件进行负载均衡的调用。
-
-* 选择器和规则，请详细看：[选择器规则](../admin/selector-and-rule)。
-
-* http配置，是网关匹配到流量以后，真实调用的http配置，可以配置多个，设置负载均衡权重，具体的负载均衡策略，在规则中指定。
- * 配置详解：
-
- * 第一个框：hostName，一般填写 `localhost`，该字段暂时没使用。
-
- * 第二个框：http协议，一般填写 `http://` 或者 `https://` ，不填写默认为:`http://`
-
- * 第三个框：ip与端口，这里填写你真实服务的 ip + 端口。
-
- * 第四个框：负载均衡权重。
-
- * ip + port 检测
-
- * 在soul-admin 会有一个定时任务来扫描 配置的ip端口，如果发现下线，则会删除该 ip + port
-
- * 可以进行如下配置 ：
-
+## 2.3 启用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为开启。
+
+
+
+## 2.4 配置插件
+
+### 2.4.1 在客户端项目配置文件中配置接入参数
+
+* 客户端接入方式和服务器地址，下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
+* 客户端配置，包含协议名称以及服务的路由地址，这里请使用 http 协议，并且必须配置 contextPath 的值作为每个服务的路由地址。
+
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http 协议
+ props:
+ contextPath: /http # 每个服务的路由地址
+```
+
+### 2.4.2 在 shenyu-admin 配置文件中配置 upstream 有效性的检测参数
+
+下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
+
+> 只有 http 类型的注册中心才支持 upstream 检测
+
```yaml
- soul.upstream.check:true 默认为 ture，设置为false，不检测
- soul.upstream.scheduledTime:10 定时检测时间间隔，默认10秒
- ```
-
+ shenyu:
+ register:
+ registerType: http # 只有 http 类型的注册中心才支持检测 upstream
+ serverLists:
+ props:
+ checked: true # 默认为 ture，设置为 false，不检测
+ zombieCheckTimes: 5 # 僵尸 upstream 最大检测次数，超过 5 次不再检测其有效性，默认为 5
+ scheduledTime: 10 # 定时检测时间间隔，默认 10 秒
+ zombieRemovalTimes: 60 # upstream 多少秒不在线认定为僵尸 upstream，默认 60 秒
+```
+
+### 2.4.3 在 shenyu-admin 配置 divide 插件的选择器和规则信息
+
+客户端启动之后会在 shenyu-admin -> 插件列表 -> Proxy -> Divide 自动注册[选择器和规则](../../user-guide/admin-usage/selector-and-rule)信息。
+
+
+#### 2.4.3.1 选择器的配置
+
+divide 选择器示例，通用选择器配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.1.1 选择器处理信息配置
+
+- `host`：填写 `localhost`，该字段暂时没使用。
+- `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- `protocol`：：`http` 协议，填写 `http://` 或者 `https://`，不填写默认为：`http://`
+- `startupTime`： 启动时间，单位毫秒。
+- `weight`：负载均衡权重，服务启动自动注册的默认值为 50。
+- `warmupTime`：预热时间，单位毫秒，在预热中的服务器会计算瞬时权重，计算值会小于实际配置的权重，以保护刚启动的服务器，服务启动注册的默认值为 10。举个例子预热时间 100 毫秒，目前启动了 50 毫秒，配置的权重 50， 实际的权重是 25。
+- `status`：开启或关闭，开始状态此处理器才有效。
+
+#### 2.4.3.2 规则的处理信息配置
+
+divide 规则示例，通用规则配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.2.1 规则处理信息配置
+
+- `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random` 和 `hash`。
+- `timeout`：调用`http`客户端的超时时间。
+- `retryCount`：调用`http`客户端超时失败的重试次数。
+- `headerMaxSize`：请求`header`的最大值。
+- `requestMaxSize`：请求体的最大值。
+- `retryStrategy`：从`2.4.3版本`开始支持，失败后的重试策略，默认`current`以保持对低版本的兼容。 比如下游有3个服务`http://localhost:1111`、`http://localhost:1112`和`http://localhost:1113`，假设第一次负载均衡到`http://localhost:1111`并且`调用失败`。使用`current`策略会继续重试调用`http://localhost:1111`；使用`failover`策略会通过`负载均衡`重试调用到其他服务如`http://localhost:1112`，此时如果又失败了，则调用到`http://localhost:1113`，直到没有可用的服务为止。
+
+## 2.5 示例
+
+### 2.5.1 示例 A/B 测试
+
+待补充
+
+### 2.5.2 示例 灰度测试
+
+待补充
+
+# 3. 如何禁用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为禁用。
+
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md
index d893c26931..a37ce85de5 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md
@@ -4,77 +4,142 @@ keywords: ["divide"]
description: divide插件
---
-## 说明
+# 1. 概述
-`divide`插件是网关用于处理 `http协议`请求的核心处理插件。
+## 1.1 插件名称
-## 插件设置
+* `divide`插件
-* 引入相关依赖，开启插件，请参考：[Http快速开始](../../quick-start/quick-start-http) 。
-
-* `Http`应用客户端接入，请参考：[Http服务接入](../../user-guide/http-proxy) 。
+## 1.2 适用场景
-## 插件讲解
+* 处理 `http协议` 请求
+* 支持流量治理，例如a/b 测试、灰度测试
+* 服务负载均衡
+* 设置接口的超时时间
-`divide`插件是进行`http`正向代理的插件，所有`http`类型的请求，都是由该插件进行负载均衡的调用。
+## 1.3 插件功能
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_example.png" width="80%" height="80%" />
+* 支持根据 uri、header、query 等请求信息做流量的治理
+* 支持设置请求的负载均衡策略，同时支持服务预热，目前支持三种策略：ip hash（带虚拟节点的一致性哈希）、round-robbin（加权轮询）、random（加权随机）
+* 支持设置接口级别请求头最大值、请求体最大值、请求超时时间
+* 支持设置超时重试策略和重试次数，目前重试策略支持：current（重试之前失败的服务器）和failover（重试其它服务器）
-客户端接入`Apache ShenYu`网关后，会自动注册选择器和规则信息，关于选择器和规则配置，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)。
+## 1.4 插件代码
+* 核心模块 ```shenyu-plugin-divide```
+* 核心类 ```org.apache.shenyu.plugin.divide.DividePlugin```
-#### 选择器处理
+# 2. 如何使用插件
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_add.png" width="80%" height="80%" />
+## 2.1 插件使用流程图
+
-选择器处理: 对应[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)的`handle`字段，是网关匹配到流量以后，真实调用的`http`配置，可以配置多个，设置负载均衡权重，具体的负载均衡策略，在规则中指定。更多信息请参考插件管理中的 [插件处理管理](../plugin-handle-explanation) 。
+## 2.2 导入 pom
-* 处理配置详解：
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置。
- * `host`：填写 `localhost`，该字段暂时没使用。
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
- * `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+## 2.3 启用插件
- * `protocol`：：`http` 协议，填写 `http://` 或者 `https://` ，不填写默认为:`http://`
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为开启。
- * `startupTime`： 启用时间。
+
- * `weight`：负载均衡权重。
+## 2.4 配置插件
- * `warmupTime`：预热时间。
+### 2.4.1 在客户端项目配置文件中配置接入参数
- * `status`：开启或关闭。
+* 客户端接入方式和服务器地址，下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
+* 客户端配置，包含协议名称以及服务的路由地址，这里请使用 http 协议，并且必须配置 contextPath 的值作为每个服务的路由地址。
- * `ip + port` 检测
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http 协议
+ props:
+ contextPath: /http # 每个服务的路由地址
+```
+
+### 2.4.2 在 shenyu-admin 配置文件中配置 upstream 有效性的检测参数
+
+下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
- * 在 `shenyu-admin` 会有一个定时任务来扫描 配置的`ip`端口，如果发现下线，则会删除该 `ip + port`
+> 只有 http 类型的注册中心才支持 upstream 检测
- * 可以进行如下配置 ：
-
```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # 默认为 ture，设置为false，不检测
- zombieCheckTimes: 5
- scheduledTime: 10 # 定时检测时间间隔，默认10秒
-
- ```
-
-#### 规则处理
-
- <img src="/img/shenyu/basicConfig/pluginHandle/rule_handle.png" width="80%" height="80%" />
-
-规则处理，即`handle`字段，是网关对流量完成最终匹配后，采取何种处理规则。更多信息请参考插件管理中的 [插件处理管理](../../user-guide/admin-usage/plugin-handle-explanation) 。
-
-* 处理配置详解：
- * `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random`和`hash`。
- * `retryCount`：调用`http`客户端的重试次数。
- * `timeout`：调用`http`客户端的超时时间。
- * `headerMaxSize`：请求的`header`的最大值。
- * `requestMaxSize`：请求体的最大值。
+ shenyu:
+ register:
+ registerType: http # 只有 http 类型的注册中心才支持检测 upstream
+ serverLists:
+ props:
+ checked: true # 默认为 ture，设置为 false，不检测
+ zombieCheckTimes: 5 # 僵尸 upstream 最大检测次数，超过 5 次不再检测其有效性，默认为 5
+ scheduledTime: 10 # 定时检测时间间隔，默认 10 秒
+ zombieRemovalTimes: 60 # upstream 多少秒不在线认定为僵尸 upstream，默认 60 秒
+```
+
+### 2.4.3 在 shenyu-admin 配置 divide 插件的选择器和规则信息
+
+客户端启动之后会在 shenyu-admin -> 插件列表 -> Proxy -> Divide 自动注册[选择器和规则](../../user-guide/admin-usage/selector-and-rule)信息。
+
+
+#### 2.4.3.1 选择器的配置
+
+divide 选择器示例，通用选择器配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.1.1 选择器处理信息配置
+
+- `host`：填写 `localhost`，该字段暂时没使用。
+- `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- `protocol`：：`http` 协议，填写 `http://` 或者 `https://`，不填写默认为：`http://`
+- `startupTime`： 启动时间，单位毫秒。
+- `weight`：负载均衡权重，服务启动自动注册的默认值为 50。
+- `warmupTime`：预热时间，单位毫秒，在预热中的服务器会计算瞬时权重，计算值会小于实际配置的权重，以保护刚启动的服务器，服务启动注册的默认值为 10。举个例子预热时间 100 毫秒，目前启动了 50 毫秒，配置的权重 50， 实际的权重是 25。
+- `status`：开启或关闭，开始状态此处理器才有效。
+
+#### 2.4.3.2 规则的处理信息配置
+
+divide 规则示例，通用规则配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.2.1 规则处理信息配置
+
+- `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random` 和 `hash`。
+- `timeout`：调用`http`客户端的超时时间。
+- `retryCount`：调用`http`客户端超时失败的重试次数。
+- `headerMaxSize`：请求`header`的最大值。
+- `requestMaxSize`：请求体的最大值。
+- `retryStrategy`：从`2.4.3版本`开始支持，失败后的重试策略，默认`current`以保持对低版本的兼容。 比如下游有3个服务`http://localhost:1111`、`http://localhost:1112`和`http://localhost:1113`，假设第一次负载均衡到`http://localhost:1111`并且`调用失败`。使用`current`策略会继续重试调用`http://localhost:1111`；使用`failover`策略会通过`负载均衡`重试调用到其他服务如`http://localhost:1112`，此时如果又失败了，则调用到`http://localhost:1113`，直到没有可用的服务为止。
+
+## 2.5 示例
+
+### 2.5.1 示例 A/B 测试
+
+待补充
+
+### 2.5.2 示例 灰度测试
+
+待补充
+
+# 3. 如何禁用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为禁用。
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/plugin-center/proxy/divide-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/plugin-center/proxy/divide-plugin.md
index c4b1c9e709..a37ce85de5 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/plugin-center/proxy/divide-plugin.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.1/plugin-center/proxy/divide-plugin.md
@@ -4,77 +4,142 @@ keywords: ["divide"]
description: divide插件
---
-## 说明
+# 1. 概述
-`divide`插件是网关用于处理 `http协议`请求的核心处理插件。
+## 1.1 插件名称
-## 插件设置
+* `divide`插件
-* 引入相关依赖，开启插件，请参考：[Http快速开始](../../quick-start/quick-start-http) 。
+## 1.2 适用场景
-* `Http`应用客户端接入，请参考：[Http服务接入](../../user-guide/http-proxy) 。
+* 处理 `http协议` 请求
+* 支持流量治理，例如a/b 测试、灰度测试
+* 服务负载均衡
+* 设置接口的超时时间
-## 插件讲解
+## 1.3 插件功能
-`divide`插件是进行`http`正向代理的插件，所有`http`类型的请求，都是由该插件进行负载均衡的调用。
+* 支持根据 uri、header、query 等请求信息做流量的治理
+* 支持设置请求的负载均衡策略，同时支持服务预热，目前支持三种策略：ip hash（带虚拟节点的一致性哈希）、round-robbin（加权轮询）、random（加权随机）
+* 支持设置接口级别请求头最大值、请求体最大值、请求超时时间
+* 支持设置超时重试策略和重试次数，目前重试策略支持：current（重试之前失败的服务器）和failover（重试其它服务器）
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_example.png" width="80%" height="80%" />
+## 1.4 插件代码
-客户端接入`Apache ShenYu`网关后，会自动注册选择器和规则信息，关于选择器和规则配置，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)。
+* 核心模块 ```shenyu-plugin-divide```
+* 核心类 ```org.apache.shenyu.plugin.divide.DividePlugin```
+# 2. 如何使用插件
-#### 选择器处理
+## 2.1 插件使用流程图
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_add.png" width="80%" height="80%" />
+
+## 2.2 导入 pom
-选择器处理: 对应[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)的`handle`字段，是网关匹配到流量以后，真实调用的`http`配置，可以配置多个，设置负载均衡权重，具体的负载均衡策略，在规则中指定。更多信息请参考插件管理中的 [插件处理管理](../plugin-handle-explanation) 。
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置。
-* 处理配置详解：
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
- * `host`：填写 `localhost`，该字段暂时没使用。
+## 2.3 启用插件
- * `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为开启。
- * `protocol`：：`http` 协议，填写 `http://` 或者 `https://` ，不填写默认为:`http://`
+
- * `startupTime`： 启用时间。
+## 2.4 配置插件
- * `weight`：负载均衡权重。
+### 2.4.1 在客户端项目配置文件中配置接入参数
- * `warmupTime`：预热时间。
+* 客户端接入方式和服务器地址，下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
+* 客户端配置，包含协议名称以及服务的路由地址，这里请使用 http 协议，并且必须配置 contextPath 的值作为每个服务的路由地址。
- * `status`：开启或关闭。
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http 协议
+ props:
+ contextPath: /http # 每个服务的路由地址
+```
- * `ip + port` 检测
+### 2.4.2 在 shenyu-admin 配置文件中配置 upstream 有效性的检测参数
- * 在 `shenyu-admin` 会有一个定时任务来扫描 配置的`ip`端口，如果发现下线，则会删除该 `ip + port`
+下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
- * 可以进行如下配置 ：
+> 只有 http 类型的注册中心才支持 upstream 检测
```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # 默认为 ture，设置为false，不检测
- zombieCheckTimes: 5
- scheduledTime: 10 # 定时检测时间间隔，默认10秒
-
- ```
-
-#### 规则处理
-
- <img src="/img/shenyu/basicConfig/pluginHandle/rule_handle.png" width="80%" height="80%" />
-
-规则处理，即`handle`字段，是网关对流量完成最终匹配后，采取何种处理规则。更多信息请参考插件管理中的 [插件处理管理](../../user-guide/admin-usage/plugin-handle-explanation) 。
-
-* 处理配置详解：
- * `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random`和`hash`。
- * `retryCount`：调用`http`客户端的重试次数。
- * `timeout`：调用`http`客户端的超时时间。
- * `headerMaxSize`：请求的`header`的最大值。
- * `requestMaxSize`：请求体的最大值。
+ shenyu:
+ register:
+ registerType: http # 只有 http 类型的注册中心才支持检测 upstream
+ serverLists:
+ props:
+ checked: true # 默认为 ture，设置为 false，不检测
+ zombieCheckTimes: 5 # 僵尸 upstream 最大检测次数，超过 5 次不再检测其有效性，默认为 5
+ scheduledTime: 10 # 定时检测时间间隔，默认 10 秒
+ zombieRemovalTimes: 60 # upstream 多少秒不在线认定为僵尸 upstream，默认 60 秒
+```
+
+### 2.4.3 在 shenyu-admin 配置 divide 插件的选择器和规则信息
+
+客户端启动之后会在 shenyu-admin -> 插件列表 -> Proxy -> Divide 自动注册[选择器和规则](../../user-guide/admin-usage/selector-and-rule)信息。
+
+
+#### 2.4.3.1 选择器的配置
+
+divide 选择器示例，通用选择器配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.1.1 选择器处理信息配置
+
+- `host`：填写 `localhost`，该字段暂时没使用。
+- `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- `protocol`：：`http` 协议，填写 `http://` 或者 `https://`，不填写默认为：`http://`
+- `startupTime`： 启动时间，单位毫秒。
+- `weight`：负载均衡权重，服务启动自动注册的默认值为 50。
+- `warmupTime`：预热时间，单位毫秒，在预热中的服务器会计算瞬时权重，计算值会小于实际配置的权重，以保护刚启动的服务器，服务启动注册的默认值为 10。举个例子预热时间 100 毫秒，目前启动了 50 毫秒，配置的权重 50， 实际的权重是 25。
+- `status`：开启或关闭，开始状态此处理器才有效。
+
+#### 2.4.3.2 规则的处理信息配置
+
+divide 规则示例，通用规则配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.2.1 规则处理信息配置
+
+- `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random` 和 `hash`。
+- `timeout`：调用`http`客户端的超时时间。
+- `retryCount`：调用`http`客户端超时失败的重试次数。
+- `headerMaxSize`：请求`header`的最大值。
+- `requestMaxSize`：请求体的最大值。
+- `retryStrategy`：从`2.4.3版本`开始支持，失败后的重试策略，默认`current`以保持对低版本的兼容。 比如下游有3个服务`http://localhost:1111`、`http://localhost:1112`和`http://localhost:1113`，假设第一次负载均衡到`http://localhost:1111`并且`调用失败`。使用`current`策略会继续重试调用`http://localhost:1111`；使用`failover`策略会通过`负载均衡`重试调用到其他服务如`http://localhost:1112`，此时如果又失败了，则调用到`http://localhost:1113`，直到没有可用的服务为止。
+
+## 2.5 示例
+
+### 2.5.1 示例 A/B 测试
+
+待补充
+
+### 2.5.2 示例 灰度测试
+
+待补充
+
+# 3. 如何禁用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为禁用。
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/plugin-center/proxy/divide-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/plugin-center/proxy/divide-plugin.md
index c4b1c9e709..a37ce85de5 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/plugin-center/proxy/divide-plugin.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.2/plugin-center/proxy/divide-plugin.md
@@ -4,77 +4,142 @@ keywords: ["divide"]
description: divide插件
---
-## 说明
+# 1. 概述
-`divide`插件是网关用于处理 `http协议`请求的核心处理插件。
+## 1.1 插件名称
-## 插件设置
+* `divide`插件
-* 引入相关依赖，开启插件，请参考：[Http快速开始](../../quick-start/quick-start-http) 。
+## 1.2 适用场景
-* `Http`应用客户端接入，请参考：[Http服务接入](../../user-guide/http-proxy) 。
+* 处理 `http协议` 请求
+* 支持流量治理，例如a/b 测试、灰度测试
+* 服务负载均衡
+* 设置接口的超时时间
-## 插件讲解
+## 1.3 插件功能
-`divide`插件是进行`http`正向代理的插件，所有`http`类型的请求，都是由该插件进行负载均衡的调用。
+* 支持根据 uri、header、query 等请求信息做流量的治理
+* 支持设置请求的负载均衡策略，同时支持服务预热，目前支持三种策略：ip hash（带虚拟节点的一致性哈希）、round-robbin（加权轮询）、random（加权随机）
+* 支持设置接口级别请求头最大值、请求体最大值、请求超时时间
+* 支持设置超时重试策略和重试次数，目前重试策略支持：current（重试之前失败的服务器）和failover（重试其它服务器）
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_example.png" width="80%" height="80%" />
+## 1.4 插件代码
-客户端接入`Apache ShenYu`网关后，会自动注册选择器和规则信息，关于选择器和规则配置，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)。
+* 核心模块 ```shenyu-plugin-divide```
+* 核心类 ```org.apache.shenyu.plugin.divide.DividePlugin```
+# 2. 如何使用插件
-#### 选择器处理
+## 2.1 插件使用流程图
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_add.png" width="80%" height="80%" />
+
+## 2.2 导入 pom
-选择器处理: 对应[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)的`handle`字段，是网关匹配到流量以后，真实调用的`http`配置，可以配置多个，设置负载均衡权重，具体的负载均衡策略，在规则中指定。更多信息请参考插件管理中的 [插件处理管理](../plugin-handle-explanation) 。
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置。
-* 处理配置详解：
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
- * `host`：填写 `localhost`，该字段暂时没使用。
+## 2.3 启用插件
- * `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为开启。
- * `protocol`：：`http` 协议，填写 `http://` 或者 `https://` ，不填写默认为:`http://`
+
- * `startupTime`： 启用时间。
+## 2.4 配置插件
- * `weight`：负载均衡权重。
+### 2.4.1 在客户端项目配置文件中配置接入参数
- * `warmupTime`：预热时间。
+* 客户端接入方式和服务器地址，下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
+* 客户端配置，包含协议名称以及服务的路由地址，这里请使用 http 协议，并且必须配置 contextPath 的值作为每个服务的路由地址。
- * `status`：开启或关闭。
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http 协议
+ props:
+ contextPath: /http # 每个服务的路由地址
+```
- * `ip + port` 检测
+### 2.4.2 在 shenyu-admin 配置文件中配置 upstream 有效性的检测参数
- * 在 `shenyu-admin` 会有一个定时任务来扫描 配置的`ip`端口，如果发现下线，则会删除该 `ip + port`
+下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
- * 可以进行如下配置 ：
+> 只有 http 类型的注册中心才支持 upstream 检测
```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # 默认为 ture，设置为false，不检测
- zombieCheckTimes: 5
- scheduledTime: 10 # 定时检测时间间隔，默认10秒
-
- ```
-
-#### 规则处理
-
- <img src="/img/shenyu/basicConfig/pluginHandle/rule_handle.png" width="80%" height="80%" />
-
-规则处理，即`handle`字段，是网关对流量完成最终匹配后，采取何种处理规则。更多信息请参考插件管理中的 [插件处理管理](../../user-guide/admin-usage/plugin-handle-explanation) 。
-
-* 处理配置详解：
- * `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random`和`hash`。
- * `retryCount`：调用`http`客户端的重试次数。
- * `timeout`：调用`http`客户端的超时时间。
- * `headerMaxSize`：请求的`header`的最大值。
- * `requestMaxSize`：请求体的最大值。
+ shenyu:
+ register:
+ registerType: http # 只有 http 类型的注册中心才支持检测 upstream
+ serverLists:
+ props:
+ checked: true # 默认为 ture，设置为 false，不检测
+ zombieCheckTimes: 5 # 僵尸 upstream 最大检测次数，超过 5 次不再检测其有效性，默认为 5
+ scheduledTime: 10 # 定时检测时间间隔，默认 10 秒
+ zombieRemovalTimes: 60 # upstream 多少秒不在线认定为僵尸 upstream，默认 60 秒
+```
+
+### 2.4.3 在 shenyu-admin 配置 divide 插件的选择器和规则信息
+
+客户端启动之后会在 shenyu-admin -> 插件列表 -> Proxy -> Divide 自动注册[选择器和规则](../../user-guide/admin-usage/selector-and-rule)信息。
+
+
+#### 2.4.3.1 选择器的配置
+
+divide 选择器示例，通用选择器配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.1.1 选择器处理信息配置
+
+- `host`：填写 `localhost`，该字段暂时没使用。
+- `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- `protocol`：：`http` 协议，填写 `http://` 或者 `https://`，不填写默认为：`http://`
+- `startupTime`： 启动时间，单位毫秒。
+- `weight`：负载均衡权重，服务启动自动注册的默认值为 50。
+- `warmupTime`：预热时间，单位毫秒，在预热中的服务器会计算瞬时权重，计算值会小于实际配置的权重，以保护刚启动的服务器，服务启动注册的默认值为 10。举个例子预热时间 100 毫秒，目前启动了 50 毫秒，配置的权重 50， 实际的权重是 25。
+- `status`：开启或关闭，开始状态此处理器才有效。
+
+#### 2.4.3.2 规则的处理信息配置
+
+divide 规则示例，通用规则配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.2.1 规则处理信息配置
+
+- `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random` 和 `hash`。
+- `timeout`：调用`http`客户端的超时时间。
+- `retryCount`：调用`http`客户端超时失败的重试次数。
+- `headerMaxSize`：请求`header`的最大值。
+- `requestMaxSize`：请求体的最大值。
+- `retryStrategy`：从`2.4.3版本`开始支持，失败后的重试策略，默认`current`以保持对低版本的兼容。 比如下游有3个服务`http://localhost:1111`、`http://localhost:1112`和`http://localhost:1113`，假设第一次负载均衡到`http://localhost:1111`并且`调用失败`。使用`current`策略会继续重试调用`http://localhost:1111`；使用`failover`策略会通过`负载均衡`重试调用到其他服务如`http://localhost:1112`，此时如果又失败了，则调用到`http://localhost:1113`，直到没有可用的服务为止。
+
+## 2.5 示例
+
+### 2.5.1 示例 A/B 测试
+
+待补充
+
+### 2.5.2 示例 灰度测试
+
+待补充
+
+# 3. 如何禁用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为禁用。
+
+
diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/plugin-center/proxy/divide-plugin.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/plugin-center/proxy/divide-plugin.md
index a01d2009cb..a37ce85de5 100644
--- a/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/plugin-center/proxy/divide-plugin.md
+++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.4.3/plugin-center/proxy/divide-plugin.md
@@ -4,85 +4,142 @@ keywords: ["divide"]
description: divide插件
---
-## 说明
+# 1. 概述
-`divide`插件是网关用于处理 `http协议`请求的核心处理插件。
+## 1.1 插件名称
-## 插件设置
+* `divide`插件
-* 引入相关依赖，开启插件，请参考：[Http快速开始](../../quick-start/quick-start-http) 。
+## 1.2 适用场景
-* `Http`应用客户端接入，请参考：[Http服务接入](../../user-guide/http-proxy) 。
+* 处理 `http协议` 请求
+* 支持流量治理，例如a/b 测试、灰度测试
+* 服务负载均衡
+* 设置接口的超时时间
-## 插件讲解
+## 1.3 插件功能
-`divide`插件是进行`http`正向代理的插件，所有`http`类型的请求，都是由该插件进行负载均衡的调用。
+* 支持根据 uri、header、query 等请求信息做流量的治理
+* 支持设置请求的负载均衡策略，同时支持服务预热，目前支持三种策略：ip hash（带虚拟节点的一致性哈希）、round-robbin（加权轮询）、random（加权随机）
+* 支持设置接口级别请求头最大值、请求体最大值、请求超时时间
+* 支持设置超时重试策略和重试次数，目前重试策略支持：current（重试之前失败的服务器）和failover（重试其它服务器）
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_example.png" width="80%" height="80%" />
+## 1.4 插件代码
-客户端接入`Apache ShenYu`网关后，会自动注册选择器和规则信息，关于选择器和规则配置，请参考：[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)。
+* 核心模块 ```shenyu-plugin-divide```
+* 核心类 ```org.apache.shenyu.plugin.divide.DividePlugin```
+# 2. 如何使用插件
-#### 选择器处理
+## 2.1 插件使用流程图
-<img src="/img/shenyu/basicConfig/pluginHandle/selector_add.png" width="80%" height="80%" />
+
+## 2.2 导入 pom
-选择器处理: 对应[选择器和规则管理](../../user-guide/admin-usage/selector-and-rule)的`handle`字段，是网关匹配到流量以后，真实调用的`http`配置，可以配置多个，设置负载均衡权重，具体的负载均衡策略，在规则中指定。更多信息请参考插件管理中的 [插件处理管理](../plugin-handle-explanation) 。
+- 在网关的 `pom.xml` 文件中添加插件 maven 配置。
-* 处理配置详解：
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
- * `host`：填写 `localhost`，该字段暂时没使用。
+## 2.3 启用插件
- * `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为开启。
- * `protocol`：：`http` 协议，填写 `http://` 或者 `https://` ，不填写默认为:`http://`
+
- * `startupTime`： 启用时间。
+## 2.4 配置插件
- * `weight`：负载均衡权重。
+### 2.4.1 在客户端项目配置文件中配置接入参数
- * `warmupTime`：预热时间。
+* 客户端接入方式和服务器地址，下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
+* 客户端配置，包含协议名称以及服务的路由地址，这里请使用 http 协议，并且必须配置 contextPath 的值作为每个服务的路由地址。
- * `status`：开启或关闭。
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http 协议
+ props:
+ contextPath: /http # 每个服务的路由地址
+```
- * `ip + port` 检测
+### 2.4.2 在 shenyu-admin 配置文件中配置 upstream 有效性的检测参数
- * 在 `shenyu-admin` 会有一个定时任务来扫描 配置的`ip`端口，如果发现下线，则会删除该 `ip + port`
+下面的示例使用了 http 接入方式，目前客户端支持的接入的方式有以下几种：http、zookeeper、etcd、nacos、consul，详细的接入配置参数请参考[客户端接入配置](../../user-guide/register-center-access)。
- * 可以进行如下配置 ：
+> 只有 http 类型的注册中心才支持 upstream 检测
```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # 默认为 ture，设置为false，不检测
- zombieCheckTimes: 5
- scheduledTime: 10 # 定时检测时间间隔，默认10秒
-
- ```
-
-#### 规则处理
-
- <img src="/img/shenyu/basicConfig/pluginHandle/rule_handle.png" width="80%" height="80%" />
-
-规则处理，即`handle`字段，是网关对流量完成最终匹配后，采取何种处理规则。更多信息请参考插件管理中的 [插件处理管理](../../user-guide/admin-usage/plugin-handle-explanation) 。
-
-* 处理配置详解：
- * `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random`和`hash`。
- * `retryCount`：调用`http`客户端的重试次数。
- * `timeout`：调用`http`客户端的超时时间。
- * `headerMaxSize`：请求的`header`的最大值。
- * `requestMaxSize`：请求体的最大值。
- * `retryStrategy`：从`2.4.3版本`开始支持，失败后的重试策略，默认`current`保持对低版本的兼容。
-
- 比如下游有3个服务`http://localhost:1111`、`http://localhost:1112`和`http://localhost:1113`，假设第一次负载均衡到`http://localhost:1111`并且`调用失败`。
-
- 使用`current`策略会继续重试调用`http://localhost:1111`；
-
- 使用`failover`策略会通过`负载均衡`重试调用到其他服务如`http://localhost:1112`，此时如果又失败了，则调用到`http://localhost:1113`，直到没有可用的服务为止。
-
\ No newline at end of file
+ shenyu:
+ register:
+ registerType: http # 只有 http 类型的注册中心才支持检测 upstream
+ serverLists:
+ props:
+ checked: true # 默认为 ture，设置为 false，不检测
+ zombieCheckTimes: 5 # 僵尸 upstream 最大检测次数，超过 5 次不再检测其有效性，默认为 5
+ scheduledTime: 10 # 定时检测时间间隔，默认 10 秒
+ zombieRemovalTimes: 60 # upstream 多少秒不在线认定为僵尸 upstream，默认 60 秒
+```
+
+### 2.4.3 在 shenyu-admin 配置 divide 插件的选择器和规则信息
+
+客户端启动之后会在 shenyu-admin -> 插件列表 -> Proxy -> Divide 自动注册[选择器和规则](../../user-guide/admin-usage/selector-and-rule)信息。
+
+
+#### 2.4.3.1 选择器的配置
+
+divide 选择器示例，通用选择器配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.1.1 选择器处理信息配置
+
+- `host`：填写 `localhost`，该字段暂时没使用。
+- `ip:port`：`ip` 与端口，这里填写你真实服务的 `ip` + 端口。
+- `protocol`：：`http` 协议，填写 `http://` 或者 `https://`，不填写默认为：`http://`
+- `startupTime`： 启动时间，单位毫秒。
+- `weight`：负载均衡权重，服务启动自动注册的默认值为 50。
+- `warmupTime`：预热时间，单位毫秒，在预热中的服务器会计算瞬时权重，计算值会小于实际配置的权重，以保护刚启动的服务器，服务启动注册的默认值为 10。举个例子预热时间 100 毫秒，目前启动了 50 毫秒，配置的权重 50， 实际的权重是 25。
+- `status`：开启或关闭，开始状态此处理器才有效。
+
+#### 2.4.3.2 规则的处理信息配置
+
+divide 规则示例，通用规则配置请参考[选择器和规则](../../user-guide/admin-usage/selector-and-rule)。
+
+
+
+##### 2.4.3.2.1 规则处理信息配置
+
+- `loadStrategy`：如果`http`客户端是一个集群，`Apache ShenYu`网关调用时采取哪种负载均衡策略，当前支持 `roundRobin`、`random` 和 `hash`。
+- `timeout`：调用`http`客户端的超时时间。
+- `retryCount`：调用`http`客户端超时失败的重试次数。
+- `headerMaxSize`：请求`header`的最大值。
+- `requestMaxSize`：请求体的最大值。
+- `retryStrategy`：从`2.4.3版本`开始支持，失败后的重试策略，默认`current`以保持对低版本的兼容。 比如下游有3个服务`http://localhost:1111`、`http://localhost:1112`和`http://localhost:1113`，假设第一次负载均衡到`http://localhost:1111`并且`调用失败`。使用`current`策略会继续重试调用`http://localhost:1111`；使用`failover`策略会通过`负载均衡`重试调用到其他服务如`http://localhost:1112`，此时如果又失败了，则调用到`http://localhost:1113`，直到没有可用的服务为止。
+
+## 2.5 示例
+
+### 2.5.1 示例 A/B 测试
+
+待补充
+
+### 2.5.2 示例 灰度测试
+
+待补充
+
+# 3. 如何禁用插件
+
+- 在 `shenyu-admin` --> 基础配置 --> 插件管理 --> `divide` 设置为禁用。
+
+
diff --git a/versioned_docs/version-2.3.0/plugins/divide-plugin.md b/versioned_docs/version-2.3.0/plugins/divide-plugin.md
index 4b1ac08a21..a44f37c2da 100755
--- a/versioned_docs/version-2.3.0/plugins/divide-plugin.md
+++ b/versioned_docs/version-2.3.0/plugins/divide-plugin.md
@@ -5,49 +5,142 @@ keywords: ["divide"]
description: divide plugin
---
-## Explanation
+# 1. Overview
-* `Divide` is the core processing plugin for gateway to process `http` requests.
+## 1.1 Plugin Name
-## Plugin Setting
+* `divide` Plugin
-* Enable plugin, `soul-admin` --> plugin management--> `divide` set to enable.
+## 1.2 Appropriate Scenario
-* Divide plugin，cooperate with `starter` to take effect，please refer to：[user-http](../users-guide/http-proxy)。
+* Handling `http protocol` requests.
+* Support traffic management, such as a/b test, grayscale test.
+* Service Load Balancing.
+* Set request timeout.
-```xml
- <!--if you use http proxy start this-->
- <dependency>
- <groupId>org.dromara</groupId>
- <artifactId>soul-spring-boot-starter-plugin-divide</artifactId>
- <version>${last.version}</version>
- </dependency>
-
- <dependency>
- <groupId>org.dromara</groupId>
- <artifactId>soul-spring-boot-starter-plugin-httpclient</artifactId>
- <version>${last.version}</version>
- </dependency>
+## 1.3 Plugin functionality
+
+* Supports traffic management based on request information such as uri, header, and query.
+* Supports setting the load balancing strategy for requests, and supports service warm-up. Currently, three strategies are supported: ip hash (consistent hash with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Supports setting the maximum value of the request header, the maximum value of the request body, and the request level timeout.
+* Supports setting the timeout retry policy and the number of retries. Currently, the retry policy supports: current (retrying the server that failed before) and failover (retrying other servers).
+
+## 1.4 Plugin Code
+
+* Core module is ```shenyu-plugin-divide```.
+* Core class is ```org.apache.shenyu.plugin.divide.DividePlugin```.
+
+# 2. How to use plugin
+## 2.1 Plugin-use procedure chart
+
+
+
+## 2.2 Import pom
+
+- Import maven in shenyu-bootstrap project's `pom.xml` file.
+
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
```
-## Plugin Detail
+## 2.3 Enable plugin
-* Divide is a plugin for http forward proxy, and all http requests are called by this plugin in load balancing.
-* Selectors and rules, please refer to: [selector](../admin/selector-and-rule).
-* Http configuration is the real invoked configuration after the gateway matches the traffic; You can set multiple configurations and concrete load balancing weights in the rules.
- * Configuration Detail:
- * The first box: hostName, generally fill in `localhost`, which is temporarily unused.
- * The second box: http protocol, usually fill in ` http:// ` or ` https:// `, if not, the default is: ` http:// `.
- * The third box: ip and port, where you fill in the ip+port of your real service.
- * The fourth box: load balancing weight.
- * Ip + Port Detection
- * In soul-admin, there is a scheduled task to scan the configured ip and port. If it is found that the ip and port is offline, it will be removed.
- * It can be configured as follows:
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status enable.
+
+
+
+## 2.4 Config plugin
+
+### 2.4.1 Configure access parameters in the client project configuration file
+
+* Client access method and server address. The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+* Client configuration, including the protocol name and the routing address of the service, please use the http protocol here, and the value of contextPath must be configured as the routing address of each service.
+
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http protocol
+ props:
+ contextPath: /http # routing address for each service
+```
+
+### 2.4.2 Configure upstream validity detection parameters in the shenyu-admin configuration file
+
+The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+> Only http-type registries support upstream detection.
```yaml
-soul.upstream.check: true //Default is ture, if setting false, program will not detect.
-soul.upstream.scheduledTime: 10 //Timing detection interval, default 10 seconds.
- ```
-
-
+ shenyu:
+ register:
+ registerType: http # Only http-type register center support upstream detection.
+ serverLists:
+ props:
+ checked: true # The default is true, set to false, do not detect.
+ zombieCheckTimes: 5 # The maximum number of zombie upstream detections. If it exceeds 5 times, its validity will no longer be detected. The default value is 5.
+ scheduledTime: 10 # Timing detection interval, the default is 10 seconds.
+ zombieRemovalTimes: 60 # How many seconds the upstream is offline to be considered as a zombie upstream, the default is 60 seconds.
+```
+
+### 2.4.3 Configure the selector and rule information of the divide plugin in shenyu-admin
+
+After the client is started, the [selector and rule](../../user-guide/admin-usage/selector-and-rule) information will be automatically registered in shenyu-admin -> Plugin List -> Proxy -> Divide.
+
+
+
+#### 2.4.3.1 Selector configuration
+
+Example of divide selector. For general selector configuration, please refer to [Selectors and Rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.1.1 Selector handling information configuration
+
+- `host`: fill in `localhost`, this field is not used currently.
+- `ip:port`: `ip` and port, fill in the `ip` + port of your real service here.
+- `protocol`: `http` protocol, fill in `http:` or `https:`, if not fill in, the default is: `http:`.
+- `startupTime`: Startup time in milliseconds.
+- `weight`: load balancing weight, the default value of service startup automatic registration is 50.
+- `warmupTime`: Warmup time, in milliseconds. The server during warmup will calculate the instantaneous weight, and the calculated value will be smaller than the actual configured weight to protect the server just started. The default value of service startup registration is 10. For example, the warm-up time is 100 milliseconds, the current startup is 50 milliseconds, the configured weight is 50, and the actual weight is 25.
+- `status`: On or off, this selector is valid only in the on state.
+
+#### 2.4.3.2 Processing information configuration of rules
+
+Example of divide rule. For general rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.2.1 Rule processing information configuration
+
+- `loadStrategy`: If the `http` client is a cluster, which load balancing strategy is used when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
+- `timeout`: The timeout for calling the `http` client.
+- `retry Count`: The number of retries that failed to call the `http` client timeout.
+- `headerMaxSize`: The maximum value of the requested `header`.
+- `requestMaxSize`: The maximum value of the request body.
+- `retryStrategy`: Supported since `2.4.3`, retry strategy after failure, default `current` to maintain compatibility with lower versions. For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`. Using the `current` strategy will continue to retry calling `http:localhost:1111`; using the `failover` strategy will retry calling other services such as `ht [...]
+
+## 2.5 Examples
+
+### 2.5.1 Example A/B Test
+
+To be added, welcome contribute.
+
+### 2.5.2 Example Grayscale Test
+
+To be added, welcome contribute.
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status disable.
+
+
diff --git a/versioned_docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md b/versioned_docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md
index f9d6a1a405..bcf2866071 100644
--- a/versioned_docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md
+++ b/versioned_docs/version-2.4.0/plugin-center/http-handle/divide-plugin.md
@@ -4,80 +4,142 @@ keywords: ["divide"]
description: divide plugin
---
-## Explanation
+# 1. Overview
-* `Divide` is the core processing plugin for gateway to process `http` requests.
+## 1.1 Plugin Name
-## Plugin Setting
+* `divide` Plugin
-* Add related dependencies and enable plugin, please refer to: [Quick start with Http](../../quick-start/quick-start-http)
+## 1.2 Appropriate Scenario
-* `Http` client access, please refer to：[Http proxy](../../user-guide/http-proxy) .
+* Handling `http protocol` requests.
+* Support traffic management, such as a/b test, grayscale test.
+* Service Load Balancing.
+* Set request timeout.
-## Plugin detail
+## 1.3 Plugin functionality
-The `divide` plugin is a plugin for forward proxying of `http`. All requests of the `http` type are called by the plugin for load balancing.
+* Supports traffic management based on request information such as uri, header, and query.
+* Supports setting the load balancing strategy for requests, and supports service warm-up. Currently, three strategies are supported: ip hash (consistent hash with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Supports setting the maximum value of the request header, the maximum value of the request body, and the request level timeout.
+* Supports setting the timeout retry policy and the number of retries. Currently, the retry policy supports: current (retrying the server that failed before) and failover (retrying other servers).
-<img src="/img/shenyu/plugin/divide/plugin-en.png" width="80%" height="80%" />
+## 1.4 Plugin Code
+* Core module is ```shenyu-plugin-divide```.
+* Core class is ```org.apache.shenyu.plugin.divide.DividePlugin```.
-After the client connects to the `Apache ShenYu` gateway, it will automatically register the selector and rule information. For the selector and rule configuration, please refer to:[Selector And Rule](../../user-guide/admin-usage/selector-and-rule)。
+# 2. How to use plugin
+## 2.1 Plugin-use procedure chart
-### Selector Handler
+
-<img src="/img/shenyu/plugin/divide/selector_en.png" width="80%" height="80%" />
+## 2.2 Import pom
+- Import maven in shenyu-bootstrap project's `pom.xml` file.
-Selector Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , it is the `http` configuration that is actually called after the gateway matches the traffic. You can configure multiple and set the load The balance weight, the specific load balancing strategy, is specified in the rules. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
-* detailed processing setting：
+## 2.3 Enable plugin
- * `host`: input `localhost`,this field is ignored.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status enable.
- * `ip:port`: ip and port, input your true service `ip` + port here.
+
- * `protocol`: `HTTP` protocol, input `http://` or `https://`, default is:`http://` .
+## 2.4 Config plugin
- * `startupTime`: enabling the time.
+### 2.4.1 Configure access parameters in the client project configuration file
- * `weight`: load balancing weight.
+* Client access method and server address. The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+* Client configuration, including the protocol name and the routing address of the service, please use the http protocol here, and the value of contextPath must be configured as the routing address of each service.
- * `warmupTime`: warm-up time.
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http protocol
+ props:
+ contextPath: /http # routing address for each service
+```
+
+### 2.4.2 Configure upstream validity detection parameters in the shenyu-admin configuration file
+
+The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+> Only http-type registries support upstream detection.
+
+```yaml
+ shenyu:
+ register:
+ registerType: http # Only http-type register center support upstream detection.
+ serverLists:
+ props:
+ checked: true # The default is true, set to false, do not detect.
+ zombieCheckTimes: 5 # The maximum number of zombie upstream detections. If it exceeds 5 times, its validity will no longer be detected. The default value is 5.
+ scheduledTime: 10 # Timing detection interval, the default is 10 seconds.
+ zombieRemovalTimes: 60 # How many seconds the upstream is offline to be considered as a zombie upstream, the default is 60 seconds.
+```
- * `status`: open or closed.
+### 2.4.3 Configure the selector and rule information of the divide plugin in shenyu-admin
- * `ip + port` check
+After the client is started, the [selector and rule](../../user-guide/admin-usage/selector-and-rule) information will be automatically registered in shenyu-admin -> Plugin List -> Proxy -> Divide.
- * there will be a scheduled task in `shenyu-admin` to scan the configured `ip` port, if it is found offline, choose to delete the `ip + port`.
+
- * can be configured as follows:
+#### 2.4.3.1 Selector configuration
-```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # default is true, set to false, no detection
- zombieCheckTimes: 5
- scheduledTime: 10 # timing detection interval, the default is 10 seconds
+Example of divide selector. For general selector configuration, please refer to [Selectors and Rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.1.1 Selector handling information configuration
+
+- `host`: fill in `localhost`, this field is not used currently.
+- `ip:port`: `ip` and port, fill in the `ip` + port of your real service here.
+- `protocol`: `http` protocol, fill in `http:` or `https:`, if not fill in, the default is: `http:`.
+- `startupTime`: Startup time in milliseconds.
+- `weight`: load balancing weight, the default value of service startup automatic registration is 50.
+- `warmupTime`: Warmup time, in milliseconds. The server during warmup will calculate the instantaneous weight, and the calculated value will be smaller than the actual configured weight to protect the server just started. The default value of service startup registration is 10. For example, the warm-up time is 100 milliseconds, the current startup is 50 milliseconds, the configured weight is 50, and the actual weight is 25.
+- `status`: On or off, this selector is valid only in the on state.
+
+#### 2.4.3.2 Processing information configuration of rules
+
+Example of divide rule. For general rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.2.1 Rule processing information configuration
+
+- `loadStrategy`: If the `http` client is a cluster, which load balancing strategy is used when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
+- `timeout`: The timeout for calling the `http` client.
+- `retry Count`: The number of retries that failed to call the `http` client timeout.
+- `headerMaxSize`: The maximum value of the requested `header`.
+- `requestMaxSize`: The maximum value of the request body.
+- `retryStrategy`: Supported since `2.4.3`, retry strategy after failure, default `current` to maintain compatibility with lower versions. For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`. Using the `current` strategy will continue to retry calling `http:localhost:1111`; using the `failover` strategy will retry calling other services such as `ht [...]
+
+## 2.5 Examples
+
+### 2.5.1 Example A/B Test
- ```
+To be added, welcome contribute.
-### Rule Handler
+### 2.5.2 Example Grayscale Test
- <img src="/img/shenyu/plugin/divide/rule_en.png" width="80%" height="80%" />
+To be added, welcome contribute.
-Rule Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule). It is the processing rule that the gateway adopts after the final matching of the traffic is completed. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+# 3. How to disable plugin
-* detailed processing setting：
- * `loadStrategy`: if the `http` client is a cluster, which load balancing strategy is adopted when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
- * `retryCount`: number of retries for calling the `http` client.
- * `timeout`: timeout period for calling the `http` client.
- * `headerMaxSize`: maximum value of the requested `header`.
- * `requestMaxSize`: maximum size of the request body.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status disable.
-
+
diff --git a/versioned_docs/version-2.4.1/plugin-center/proxy/divide-plugin.md b/versioned_docs/version-2.4.1/plugin-center/proxy/divide-plugin.md
index 24c72e56c3..bcf2866071 100644
--- a/versioned_docs/version-2.4.1/plugin-center/proxy/divide-plugin.md
+++ b/versioned_docs/version-2.4.1/plugin-center/proxy/divide-plugin.md
@@ -4,80 +4,142 @@ keywords: ["divide"]
description: divide plugin
---
-## Explanation
+# 1. Overview
-* `Divide` is the core processing plugin for gateway to process `http` requests.
+## 1.1 Plugin Name
-## Plugin Setting
+* `divide` Plugin
-* Add related dependencies and enable plugin, please refer to: [Quick start with Http](../../quick-start/quick-start-http)
+## 1.2 Appropriate Scenario
-* `Http` client access, please refer to：[Http proxy](../../user-guide/http-proxy) .
+* Handling `http protocol` requests.
+* Support traffic management, such as a/b test, grayscale test.
+* Service Load Balancing.
+* Set request timeout.
-## Plugin detail
+## 1.3 Plugin functionality
-The `divide` plugin is a plugin for forward proxying of `http`. All requests of the `http` type are called by the plugin for load balancing.
+* Supports traffic management based on request information such as uri, header, and query.
+* Supports setting the load balancing strategy for requests, and supports service warm-up. Currently, three strategies are supported: ip hash (consistent hash with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Supports setting the maximum value of the request header, the maximum value of the request body, and the request level timeout.
+* Supports setting the timeout retry policy and the number of retries. Currently, the retry policy supports: current (retrying the server that failed before) and failover (retrying other servers).
-<img src="/img/shenyu/plugin/divide/plugin-en.png" width="80%" height="80%" />
+## 1.4 Plugin Code
+* Core module is ```shenyu-plugin-divide```.
+* Core class is ```org.apache.shenyu.plugin.divide.DividePlugin```.
-After the client connects to the `Apache ShenYu` gateway, it will automatically register the selector and rule information. For the selector and rule configuration, please refer to:[Selector And Rule](../../user-guide/admin-usage/selector-and-rule)。
+# 2. How to use plugin
+## 2.1 Plugin-use procedure chart
-#### Selector Handler
+
-<img src="/img/shenyu/plugin/divide/selector_en.png" width="80%" height="80%" />
+## 2.2 Import pom
+- Import maven in shenyu-bootstrap project's `pom.xml` file.
-Selector Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , it is the `http` configuration that is actually called after the gateway matches the traffic. You can configure multiple and set the load The balance weight, the specific load balancing strategy, is specified in the rules. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
-* detailed processing setting：
+## 2.3 Enable plugin
- * `host`: input `localhost`,this field is ignored.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status enable.
- * `ip:port`: ip and port, input your true service `ip` + port here.
+
- * `protocol`: `HTTP` protocol, input `http://` or `https://`, default is:`http://` .
+## 2.4 Config plugin
- * `startupTime`: enabling the time.
+### 2.4.1 Configure access parameters in the client project configuration file
- * `weight`: load balancing weight.
+* Client access method and server address. The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+* Client configuration, including the protocol name and the routing address of the service, please use the http protocol here, and the value of contextPath must be configured as the routing address of each service.
- * `warmupTime`: warm-up time.
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http protocol
+ props:
+ contextPath: /http # routing address for each service
+```
+
+### 2.4.2 Configure upstream validity detection parameters in the shenyu-admin configuration file
+
+The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+> Only http-type registries support upstream detection.
+
+```yaml
+ shenyu:
+ register:
+ registerType: http # Only http-type register center support upstream detection.
+ serverLists:
+ props:
+ checked: true # The default is true, set to false, do not detect.
+ zombieCheckTimes: 5 # The maximum number of zombie upstream detections. If it exceeds 5 times, its validity will no longer be detected. The default value is 5.
+ scheduledTime: 10 # Timing detection interval, the default is 10 seconds.
+ zombieRemovalTimes: 60 # How many seconds the upstream is offline to be considered as a zombie upstream, the default is 60 seconds.
+```
- * `status`: open or closed.
+### 2.4.3 Configure the selector and rule information of the divide plugin in shenyu-admin
- * `ip + port` check
+After the client is started, the [selector and rule](../../user-guide/admin-usage/selector-and-rule) information will be automatically registered in shenyu-admin -> Plugin List -> Proxy -> Divide.
- * there will be a scheduled task in `shenyu-admin` to scan the configured `ip` port, if it is found offline, choose to delete the `ip + port`.
+
- * can be configured as follows:
+#### 2.4.3.1 Selector configuration
-```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # default is true, set to false, no detection
- zombieCheckTimes: 5
- scheduledTime: 10 # timing detection interval, the default is 10 seconds
+Example of divide selector. For general selector configuration, please refer to [Selectors and Rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.1.1 Selector handling information configuration
+
+- `host`: fill in `localhost`, this field is not used currently.
+- `ip:port`: `ip` and port, fill in the `ip` + port of your real service here.
+- `protocol`: `http` protocol, fill in `http:` or `https:`, if not fill in, the default is: `http:`.
+- `startupTime`: Startup time in milliseconds.
+- `weight`: load balancing weight, the default value of service startup automatic registration is 50.
+- `warmupTime`: Warmup time, in milliseconds. The server during warmup will calculate the instantaneous weight, and the calculated value will be smaller than the actual configured weight to protect the server just started. The default value of service startup registration is 10. For example, the warm-up time is 100 milliseconds, the current startup is 50 milliseconds, the configured weight is 50, and the actual weight is 25.
+- `status`: On or off, this selector is valid only in the on state.
+
+#### 2.4.3.2 Processing information configuration of rules
+
+Example of divide rule. For general rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.2.1 Rule processing information configuration
+
+- `loadStrategy`: If the `http` client is a cluster, which load balancing strategy is used when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
+- `timeout`: The timeout for calling the `http` client.
+- `retry Count`: The number of retries that failed to call the `http` client timeout.
+- `headerMaxSize`: The maximum value of the requested `header`.
+- `requestMaxSize`: The maximum value of the request body.
+- `retryStrategy`: Supported since `2.4.3`, retry strategy after failure, default `current` to maintain compatibility with lower versions. For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`. Using the `current` strategy will continue to retry calling `http:localhost:1111`; using the `failover` strategy will retry calling other services such as `ht [...]
+
+## 2.5 Examples
+
+### 2.5.1 Example A/B Test
- ```
+To be added, welcome contribute.
-#### Rule Handler
+### 2.5.2 Example Grayscale Test
- <img src="/img/shenyu/plugin/divide/rule_en.png" width="80%" height="80%" />
+To be added, welcome contribute.
-Rule Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule). It is the processing rule that the gateway adopts after the final matching of the traffic is completed. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+# 3. How to disable plugin
-* detailed processing setting：
- * `loadStrategy`: if the `http` client is a cluster, which load balancing strategy is adopted when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
- * `retryCount`: number of retries for calling the `http` client.
- * `timeout`: timeout period for calling the `http` client.
- * `headerMaxSize`: maximum value of the requested `header`.
- * `requestMaxSize`: maximum size of the request body.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status disable.
-
+
diff --git a/versioned_docs/version-2.4.2/plugin-center/proxy/divide-plugin.md b/versioned_docs/version-2.4.2/plugin-center/proxy/divide-plugin.md
index 24c72e56c3..bcf2866071 100644
--- a/versioned_docs/version-2.4.2/plugin-center/proxy/divide-plugin.md
+++ b/versioned_docs/version-2.4.2/plugin-center/proxy/divide-plugin.md
@@ -4,80 +4,142 @@ keywords: ["divide"]
description: divide plugin
---
-## Explanation
+# 1. Overview
-* `Divide` is the core processing plugin for gateway to process `http` requests.
+## 1.1 Plugin Name
-## Plugin Setting
+* `divide` Plugin
-* Add related dependencies and enable plugin, please refer to: [Quick start with Http](../../quick-start/quick-start-http)
+## 1.2 Appropriate Scenario
-* `Http` client access, please refer to：[Http proxy](../../user-guide/http-proxy) .
+* Handling `http protocol` requests.
+* Support traffic management, such as a/b test, grayscale test.
+* Service Load Balancing.
+* Set request timeout.
-## Plugin detail
+## 1.3 Plugin functionality
-The `divide` plugin is a plugin for forward proxying of `http`. All requests of the `http` type are called by the plugin for load balancing.
+* Supports traffic management based on request information such as uri, header, and query.
+* Supports setting the load balancing strategy for requests, and supports service warm-up. Currently, three strategies are supported: ip hash (consistent hash with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Supports setting the maximum value of the request header, the maximum value of the request body, and the request level timeout.
+* Supports setting the timeout retry policy and the number of retries. Currently, the retry policy supports: current (retrying the server that failed before) and failover (retrying other servers).
-<img src="/img/shenyu/plugin/divide/plugin-en.png" width="80%" height="80%" />
+## 1.4 Plugin Code
+* Core module is ```shenyu-plugin-divide```.
+* Core class is ```org.apache.shenyu.plugin.divide.DividePlugin```.
-After the client connects to the `Apache ShenYu` gateway, it will automatically register the selector and rule information. For the selector and rule configuration, please refer to:[Selector And Rule](../../user-guide/admin-usage/selector-and-rule)。
+# 2. How to use plugin
+## 2.1 Plugin-use procedure chart
-#### Selector Handler
+
-<img src="/img/shenyu/plugin/divide/selector_en.png" width="80%" height="80%" />
+## 2.2 Import pom
+- Import maven in shenyu-bootstrap project's `pom.xml` file.
-Selector Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , it is the `http` configuration that is actually called after the gateway matches the traffic. You can configure multiple and set the load The balance weight, the specific load balancing strategy, is specified in the rules. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
-* detailed processing setting：
+## 2.3 Enable plugin
- * `host`: input `localhost`,this field is ignored.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status enable.
- * `ip:port`: ip and port, input your true service `ip` + port here.
+
- * `protocol`: `HTTP` protocol, input `http://` or `https://`, default is:`http://` .
+## 2.4 Config plugin
- * `startupTime`: enabling the time.
+### 2.4.1 Configure access parameters in the client project configuration file
- * `weight`: load balancing weight.
+* Client access method and server address. The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+* Client configuration, including the protocol name and the routing address of the service, please use the http protocol here, and the value of contextPath must be configured as the routing address of each service.
- * `warmupTime`: warm-up time.
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http protocol
+ props:
+ contextPath: /http # routing address for each service
+```
+
+### 2.4.2 Configure upstream validity detection parameters in the shenyu-admin configuration file
+
+The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+> Only http-type registries support upstream detection.
+
+```yaml
+ shenyu:
+ register:
+ registerType: http # Only http-type register center support upstream detection.
+ serverLists:
+ props:
+ checked: true # The default is true, set to false, do not detect.
+ zombieCheckTimes: 5 # The maximum number of zombie upstream detections. If it exceeds 5 times, its validity will no longer be detected. The default value is 5.
+ scheduledTime: 10 # Timing detection interval, the default is 10 seconds.
+ zombieRemovalTimes: 60 # How many seconds the upstream is offline to be considered as a zombie upstream, the default is 60 seconds.
+```
- * `status`: open or closed.
+### 2.4.3 Configure the selector and rule information of the divide plugin in shenyu-admin
- * `ip + port` check
+After the client is started, the [selector and rule](../../user-guide/admin-usage/selector-and-rule) information will be automatically registered in shenyu-admin -> Plugin List -> Proxy -> Divide.
- * there will be a scheduled task in `shenyu-admin` to scan the configured `ip` port, if it is found offline, choose to delete the `ip + port`.
+
- * can be configured as follows:
+#### 2.4.3.1 Selector configuration
-```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # default is true, set to false, no detection
- zombieCheckTimes: 5
- scheduledTime: 10 # timing detection interval, the default is 10 seconds
+Example of divide selector. For general selector configuration, please refer to [Selectors and Rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.1.1 Selector handling information configuration
+
+- `host`: fill in `localhost`, this field is not used currently.
+- `ip:port`: `ip` and port, fill in the `ip` + port of your real service here.
+- `protocol`: `http` protocol, fill in `http:` or `https:`, if not fill in, the default is: `http:`.
+- `startupTime`: Startup time in milliseconds.
+- `weight`: load balancing weight, the default value of service startup automatic registration is 50.
+- `warmupTime`: Warmup time, in milliseconds. The server during warmup will calculate the instantaneous weight, and the calculated value will be smaller than the actual configured weight to protect the server just started. The default value of service startup registration is 10. For example, the warm-up time is 100 milliseconds, the current startup is 50 milliseconds, the configured weight is 50, and the actual weight is 25.
+- `status`: On or off, this selector is valid only in the on state.
+
+#### 2.4.3.2 Processing information configuration of rules
+
+Example of divide rule. For general rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.2.1 Rule processing information configuration
+
+- `loadStrategy`: If the `http` client is a cluster, which load balancing strategy is used when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
+- `timeout`: The timeout for calling the `http` client.
+- `retry Count`: The number of retries that failed to call the `http` client timeout.
+- `headerMaxSize`: The maximum value of the requested `header`.
+- `requestMaxSize`: The maximum value of the request body.
+- `retryStrategy`: Supported since `2.4.3`, retry strategy after failure, default `current` to maintain compatibility with lower versions. For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`. Using the `current` strategy will continue to retry calling `http:localhost:1111`; using the `failover` strategy will retry calling other services such as `ht [...]
+
+## 2.5 Examples
+
+### 2.5.1 Example A/B Test
- ```
+To be added, welcome contribute.
-#### Rule Handler
+### 2.5.2 Example Grayscale Test
- <img src="/img/shenyu/plugin/divide/rule_en.png" width="80%" height="80%" />
+To be added, welcome contribute.
-Rule Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule). It is the processing rule that the gateway adopts after the final matching of the traffic is completed. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+# 3. How to disable plugin
-* detailed processing setting：
- * `loadStrategy`: if the `http` client is a cluster, which load balancing strategy is adopted when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
- * `retryCount`: number of retries for calling the `http` client.
- * `timeout`: timeout period for calling the `http` client.
- * `headerMaxSize`: maximum value of the requested `header`.
- * `requestMaxSize`: maximum size of the request body.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status disable.
-
+
diff --git a/versioned_docs/version-2.4.3/plugin-center/proxy/divide-plugin.md b/versioned_docs/version-2.4.3/plugin-center/proxy/divide-plugin.md
index 16a79ad237..bcf2866071 100644
--- a/versioned_docs/version-2.4.3/plugin-center/proxy/divide-plugin.md
+++ b/versioned_docs/version-2.4.3/plugin-center/proxy/divide-plugin.md
@@ -4,86 +4,142 @@ keywords: ["divide"]
description: divide plugin
---
-## Explanation
+# 1. Overview
-* `Divide` is the core processing plugin for gateway to process `http` requests.
+## 1.1 Plugin Name
-## Plugin Setting
+* `divide` Plugin
-* Add related dependencies and enable plugin, please refer to: [Quick start with Http](../../quick-start/quick-start-http)
+## 1.2 Appropriate Scenario
-* `Http` client access, please refer to：[Http proxy](../../user-guide/http-proxy) .
+* Handling `http protocol` requests.
+* Support traffic management, such as a/b test, grayscale test.
+* Service Load Balancing.
+* Set request timeout.
-## Plugin detail
+## 1.3 Plugin functionality
-The `divide` plugin is a plugin for forward proxying of `http`. All requests of the `http` type are called by the plugin for load balancing.
+* Supports traffic management based on request information such as uri, header, and query.
+* Supports setting the load balancing strategy for requests, and supports service warm-up. Currently, three strategies are supported: ip hash (consistent hash with virtual nodes), round-robbin (weighted polling), random (weighted random).
+* Supports setting the maximum value of the request header, the maximum value of the request body, and the request level timeout.
+* Supports setting the timeout retry policy and the number of retries. Currently, the retry policy supports: current (retrying the server that failed before) and failover (retrying other servers).
-<img src="/img/shenyu/plugin/divide/plugin-en.png" width="80%" height="80%" />
+## 1.4 Plugin Code
+* Core module is ```shenyu-plugin-divide```.
+* Core class is ```org.apache.shenyu.plugin.divide.DividePlugin```.
-After the client connects to the `Apache ShenYu` gateway, it will automatically register the selector and rule information. For the selector and rule configuration, please refer to:[Selector And Rule](../../user-guide/admin-usage/selector-and-rule)。
+# 2. How to use plugin
+## 2.1 Plugin-use procedure chart
-#### Selector Handler
+
-<img src="/img/shenyu/plugin/divide/selector_en.png" width="80%" height="80%" />
+## 2.2 Import pom
+- Import maven in shenyu-bootstrap project's `pom.xml` file.
-Selector Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule) , it is the `http` configuration that is actually called after the gateway matches the traffic. You can configure multiple and set the load The balance weight, the specific load balancing strategy, is specified in the rules. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
+```xml
+ <dependency>
+ <groupId>org.apache.shenyu</groupId>
+ <artifactId>shenyu-spring-boot-starter-gateway</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+```
-* detailed processing setting：
+## 2.3 Enable plugin
- * `host`: input `localhost`,this field is ignored.
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status enable.
- * `ip:port`: ip and port, input your true service `ip` + port here.
+
- * `protocol`: `HTTP` protocol, input `http://` or `https://`, default is:`http://` .
+## 2.4 Config plugin
- * `startupTime`: enabling the time.
+### 2.4.1 Configure access parameters in the client project configuration file
- * `weight`: load balancing weight.
+* Client access method and server address. The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+* Client configuration, including the protocol name and the routing address of the service, please use the http protocol here, and the value of contextPath must be configured as the routing address of each service.
- * `warmupTime`: warm-up time.
+```yaml
+ shenyu:
+ register:
+ registerType: http
+ serverLists: http://localhost:9095
+ props:
+ username: admin
+ password: 123456
+ client:
+ http: # http protocol
+ props:
+ contextPath: /http # routing address for each service
+```
+
+### 2.4.2 Configure upstream validity detection parameters in the shenyu-admin configuration file
+
+The following example uses the http access method. Currently, the client supports the following access methods: http, zookeeper, etcd, nacos, consul. For detailed access configuration parameters, please refer to [Client Access Configuration](../../user-guide/register-center-access).
+> Only http-type registries support upstream detection.
- * `status`: open or closed.
+```yaml
+ shenyu:
+ register:
+ registerType: http # Only http-type register center support upstream detection.
+ serverLists:
+ props:
+ checked: true # The default is true, set to false, do not detect.
+ zombieCheckTimes: 5 # The maximum number of zombie upstream detections. If it exceeds 5 times, its validity will no longer be detected. The default value is 5.
+ scheduledTime: 10 # Timing detection interval, the default is 10 seconds.
+ zombieRemovalTimes: 60 # How many seconds the upstream is offline to be considered as a zombie upstream, the default is 60 seconds.
+```
- * `ip + port` check
+### 2.4.3 Configure the selector and rule information of the divide plugin in shenyu-admin
- * there will be a scheduled task in `shenyu-admin` to scan the configured `ip` port, if it is found offline, choose to delete the `ip + port`.
+After the client is started, the [selector and rule](../../user-guide/admin-usage/selector-and-rule) information will be automatically registered in shenyu-admin -> Plugin List -> Proxy -> Divide.
- * can be configured as follows:
+
-```yaml
-shenyu:
- register:
- registerType: http
- serverLists:
- props:
- sessionTimeout: 5000
- connectionTimeout: 2000
- checked: true # default is true, set to false, no detection
- zombieCheckTimes: 5
- scheduledTime: 10 # timing detection interval, the default is 10 seconds
-
- ```
-
-#### Rule Handler
-
- <img src="/img/shenyu/plugin/divide/rule_en.png" width="80%" height="80%" />
-
-Rule Handler, corresponding to the `handle` field of [Selector And Rule Config](../../user-guide/admin-usage/selector-and-rule). It is the processing rule that the gateway adopts after the final matching of the traffic is completed. For more information, please refer to [Plugin handle management](../../user-guide/admin-usage/plugin-handle-explanation) in Plugin Config.
-
-* detailed processing setting：
- * `loadStrategy`: if the `http` client is a cluster, which load balancing strategy is adopted when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
- * `retryCount`: number of retries for calling the `http` client.
- * `timeout`: timeout period for calling the `http` client.
- * `headerMaxSize`: maximum value of the requested `header`.
- * `requestMaxSize`: maximum size of the request body.
- * `retryStrategy`: supported since `2.4.3`, the retry strategy `after failure`, the default `current` remains compatible with lower versions.
-
- For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`.
-
- Using the `current` policy will continue to retry the call to `http:localhost:1111`;
-
- Using the `failover` policy will retry the call to other services such as `http:localhost:1112` through the `loadStrategy`, if it fails again at this time , call to `http:localhost:1113` until no service is available.
-
\ No newline at end of file
+#### 2.4.3.1 Selector configuration
+
+Example of divide selector. For general selector configuration, please refer to [Selectors and Rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.1.1 Selector handling information configuration
+
+- `host`: fill in `localhost`, this field is not used currently.
+- `ip:port`: `ip` and port, fill in the `ip` + port of your real service here.
+- `protocol`: `http` protocol, fill in `http:` or `https:`, if not fill in, the default is: `http:`.
+- `startupTime`: Startup time in milliseconds.
+- `weight`: load balancing weight, the default value of service startup automatic registration is 50.
+- `warmupTime`: Warmup time, in milliseconds. The server during warmup will calculate the instantaneous weight, and the calculated value will be smaller than the actual configured weight to protect the server just started. The default value of service startup registration is 10. For example, the warm-up time is 100 milliseconds, the current startup is 50 milliseconds, the configured weight is 50, and the actual weight is 25.
+- `status`: On or off, this selector is valid only in the on state.
+
+#### 2.4.3.2 Processing information configuration of rules
+
+Example of divide rule. For general rule configuration, please refer to [selectors and rules](../../user-guide/admin-usage/selector-and-rule).
+
+
+
+##### 2.4.3.2.1 Rule processing information configuration
+
+- `loadStrategy`: If the `http` client is a cluster, which load balancing strategy is used when the `Apache ShenYu` gateway is called, currently supports `roundRobin`, `random` and `hash`.
+- `timeout`: The timeout for calling the `http` client.
+- `retry Count`: The number of retries that failed to call the `http` client timeout.
+- `headerMaxSize`: The maximum value of the requested `header`.
+- `requestMaxSize`: The maximum value of the request body.
+- `retryStrategy`: Supported since `2.4.3`, retry strategy after failure, default `current` to maintain compatibility with lower versions. For example, there are 3 downstream services `http:localhost:1111`, `http:localhost:1112` and `http:localhost:1113`, assuming the first load balancing to `http:localhost:1111` and `call failed`. Using the `current` strategy will continue to retry calling `http:localhost:1111`; using the `failover` strategy will retry calling other services such as `ht [...]
+
+## 2.5 Examples
+
+### 2.5.1 Example A/B Test
+
+To be added, welcome contribute.
+
+### 2.5.2 Example Grayscale Test
+
+To be added, welcome contribute.
+
+# 3. How to disable plugin
+
+- In `shenyu-admin` --> BasicConfig --> Plugin --> `divide` set Status disable.
+
+