[dubbo-website] branch master updated: Add Migration Rule Docs (#910)

[al...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

albumenj pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 838beea  Add Migration Rule Docs (#910)
838beea is described below

commit 838beeaef20feed87079b7a8dfd355a1566702b3
Author: Albumen Kevin <jh...@gmail.com>
AuthorDate: Thu Aug 26 11:12:59 2021 +0800

    Add Migration Rule Docs (#910)
---
 content/zh/docs/migration/migration-routingrule.md      |   2 +-
 content/zh/docs/migration/migration-rule.md             | Bin 0 -> 10967 bytes
 .../zh/docs/migration/migration-service-discovery.md    |   6 +++---
 content/zh/docs/migration/migration-triple.md           |   2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/zh/docs/migration/migration-routingrule.md b/content/zh/docs/migration/migration-routingrule.md
index 2bb4724..f729e34 100644
--- a/content/zh/docs/migration/migration-routingrule.md
+++ b/content/zh/docs/migration/migration-routingrule.md
@@ -2,7 +2,7 @@
 type: docs
 title: "统一路由规则升级指南"
 linkTitle: "路由规则"
-weight: 4
+weight: 5
 description: "统一路由规则升级指南"
 ---
 
diff --git a/content/zh/docs/migration/migration-rule.md b/content/zh/docs/migration/migration-rule.md
new file mode 100644
index 0000000..0359d2c
Binary files /dev/null and b/content/zh/docs/migration/migration-rule.md differ
diff --git a/content/zh/docs/migration/migration-service-discovery.md b/content/zh/docs/migration/migration-service-discovery.md
index 0159dda..acf9fd7 100644
--- a/content/zh/docs/migration/migration-service-discovery.md
+++ b/content/zh/docs/migration/migration-service-discovery.md
@@ -36,7 +36,7 @@ description: "本文档专门针对使用 2.x 版本的老用户，详细阐述
 
 ```text
 -Ddubbo.application.register-mode=all
-# 可选值 interface、instance、all，默认是 interface，即只注册接口级地址
+# 可选值 interface、instance、all，默认是 all，即接口级地址、应用级地址都注册
 ```
 
 
@@ -126,7 +126,6 @@ ClusterInvoker 筛选的依据，可以通过 MigrationAddressComparator SPI 自
 
 除了全局的迁移策略之外，Dubbo 在消费端提供了更细粒度的迁移策略支持。控制单位可以是某一个消费者应用，它消费的服务A、服务B可以有各自独立的迁移策略，具体是用方式是在消费端配置迁移规则：
 
-在 classpath 下增加 dubbo-migration.yml 配置
 
 ```yaml
 key: demo-consumer
@@ -139,7 +138,8 @@ services:
    step: FORCE_INTERFACE
 ```
 
-使用这种方式能做到比较精细迁移控制，但是当下及后续的改造成本会比较高，除了一些特别场景，我们不太推荐启用这种配置方式。**官方推荐使用的全局的开关式的迁移策略，让消费端实例在启动阶段自行决策使用哪份可用的地址列表。**
+使用这种方式能做到比较精细迁移控制，但是当下及后续的改造成本会比较高，除了一些特别场景，我们不太推荐启用这种配置方式。
+([迁移指南](../migration-rule/)) **官方推荐使用的全局的开关式的迁移策略，让消费端实例在启动阶段自行决策使用哪份可用的地址列表。**
 
 
 
diff --git a/content/zh/docs/migration/migration-triple.md b/content/zh/docs/migration/migration-triple.md
index 3de54cc..1b71ad0 100644
--- a/content/zh/docs/migration/migration-triple.md
+++ b/content/zh/docs/migration/migration-triple.md
@@ -2,7 +2,7 @@
 type: docs
 title: "Triple协议迁移指南"
 linkTitle: "Triple"
-weight: 3
+weight: 4
 description: "Triple协议迁移指南"
 ---