[doris-website] branch master updated: upgrade fix

[ji...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 0de6969247 upgrade fix
0de6969247 is described below

commit 0de69692471ea4a41fbbe39509baa0ad4bae3416
Author: jiafeng.zhang <zh...@gmail.com>
AuthorDate: Fri Jul 22 11:43:42 2022 +0800

    upgrade fix
    
    upgrade fix
---
 docs/admin-manual/cluster-management/upgrade.md                    | 7 +++++++
 .../current/admin-manual/cluster-management/upgrade.md             | 6 ++++++
 2 files changed, 13 insertions(+)

diff --git a/docs/admin-manual/cluster-management/upgrade.md b/docs/admin-manual/cluster-management/upgrade.md
index a521bbdfd0..34eaada8bb 100644
--- a/docs/admin-manual/cluster-management/upgrade.md
+++ b/docs/admin-manual/cluster-management/upgrade.md
@@ -86,3 +86,10 @@ Doris can upgrade smoothly by rolling upgrades. The following steps are recommen
 1. Confirm that the new version of the file is deployed. Restart FE and BE instances one by one.
 2. It is suggested that BE be restarted one by one and FE be restarted one by one. Because Doris usually guarantees backward compatibility between FE and BE, that is, the old version of FE can access the new version of BE. However, the old version of BE may not be supported to access the new version of FE.
 3. It is recommended to restart the next instance after confirming the previous instance started successfully. Refer to the Installation Deployment Document for the identification of successful instance startup.
+
+## About version rollback
+Because the database is a stateful service, Doris cannot support version rollback (version downgrade) in most cases. In some cases, the rollback of the 3-bit or 4-bit version can be supported, but the rollback of the 2-bit version will not be supported.
+
+Therefore, it is recommended to upgrade some nodes and observe the business operation (gray upgrade) to reduce the upgrade risk.
+
+**Illegal rollback operation may cause data loss and damage.** 
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/upgrade.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/upgrade.md
index c586622d78..376bf5ece2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/upgrade.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/admin-manual/cluster-management/upgrade.md
@@ -86,3 +86,9 @@ Doris 可以通过滚动升级的方式，平滑进行升级。建议按照以
 1. 确认新版本的文件部署完成后。逐台重启 FE 和 BE 实例即可。
 2. 建议逐台重启 BE 后，再逐台重启 FE。因为通常 Doris 保证 FE 到 BE 的向后兼容性，即老版本的 FE 可以访问新版本的 BE。但可能不支持老版本的 BE 访问新版本的 FE。
 3. 建议确认前一个实例启动成功后，再重启下一个实例。实例启动成功的标识，请参阅安装部署文档。
+
+## 关于版本回滚
+因为数据库是一个有状态的服务，所以在大多数情况下，Doris 无法支持版本回滚（版本降级）。在某些情况下，可以支持 3 位或 4 位版本的回滚，但不会支持 2 位版本的回滚。
+所以建议通过先升级部分节点并观察业务运行情况的方式（灰度升级）来降低升级风险。
+
+**非法的回滚操作可能导致数据丢失和损坏。**


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org