From 718edb126ae0572cdfd4249a117f6078462092f7 Mon Sep 17 00:00:00 2001 From: Shiori Date: Tue, 22 Feb 2022 17:49:15 +0800 Subject: [PATCH 01/16] add rn 1.3.1 --- zh/TOC.md | 1 + zh/releases/release-1.3.0-beta.1.md | 21 +++++++++++++++ zh/releases/release-1.3.0.md | 21 +++++++++++++++ zh/releases/release-1.3.1.md | 41 +++++++++++++++++++++++++++++ zh/whats-new-in-v1.3.md | 21 +++++++++++++++ 5 files changed, 105 insertions(+) create mode 100644 zh/releases/release-1.3.1.md diff --git a/zh/TOC.md b/zh/TOC.md index 6d21bd9258..14bdf74032 100644 --- a/zh/TOC.md +++ b/zh/TOC.md @@ -115,6 +115,7 @@ - [Kubernetes 监控与告警](monitor-kubernetes.md) - 版本发布历史 - v1.3 + - [1.3.1](releases/release-1.3.1.md) - [1.3 GA](releases/release-1.3.0.md) - [1.3.0-beta.1](releases/release-1.3.0-beta.1.md) - v1.2 diff --git a/zh/releases/release-1.3.0-beta.1.md b/zh/releases/release-1.3.0-beta.1.md index 928ef8f756..2ad3158494 100644 --- a/zh/releases/release-1.3.0-beta.1.md +++ b/zh/releases/release-1.3.0-beta.1.md @@ -16,6 +16,27 @@ TiDB Operator 版本：1.3.0-beta.1 1. 在各组件的配置中，使用 `baseImage` 与 `version` 字段代替当前使用的 `image` 字段，可以参考文档[部署配置](../configure-a-tidb-cluster.md#版本)。 2. 升级 TiDB Operator。 +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，部署 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator 情况下，直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 Operator 执行升级操作。 + + 如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator，那么你需要执行以下操作来升级 TiFlash： + + 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + + 2. 升级 TiFlash + ## 滚动升级改动 - 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更，如果使用 v1.2 版本 TiDB Operator 部署了 v5.4 及更新版本的 TiDB 集群，升级 TiDB Operator 到 v1.3.0-beta.1 版本会导致 TiFlash 组件滚动更新。建议在升级 TiDB 集群到 v5.4.0 或更新版本之前，先升级 TiDB Operator 到 v1.3 及以上版本。 diff --git a/zh/releases/release-1.3.0.md b/zh/releases/release-1.3.0.md index 9537cf3cc0..52b46e33e8 100644 --- a/zh/releases/release-1.3.0.md +++ b/zh/releases/release-1.3.0.md @@ -15,6 +15,27 @@ TiDB Operator 版本：1.3.0 2. 添加新的 `spec.acrossK8s` 字段到 TidbCluster 定义，其值设置为 `true`。 3. 升级 TiDB Operator。 +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，部署 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator 情况下，直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 Operator 执行升级操作。 + + 如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator，那么你需要执行以下操作来升级 TiFlash： + + 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + + 2. 升级 TiFlash + ## 新功能 - 添加新的 `spec.tidb.tlsClient.skipInternalClientCA` 字段，以支持内部组件访问 TiDB 时跳过服务端证书验证 ([#4388](https://github.com/pingcap/tidb-operator/pull/4388), [@just1900](https://github.com/just1900)) diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md new file mode 100644 index 0000000000..887eac573b --- /dev/null +++ b/zh/releases/release-1.3.1.md @@ -0,0 +1,41 @@ +--- +title: TiDB Operator 1.3.0 Release Notes +--- + +# TiDB Operator 1.3.0 Release Notes + +发布日期: 2022 年 2 月 15 日 + +TiDB Operator 版本：1.3.0 + +## 兼容性改动 + +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 和 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 Operator，以防止 TiFlash 丢失数据： + + 1. 如果 TidbCluster 定义中未配置 TiFlash 配置中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则添加 `storage.raft.dir` 字段。 + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + [storage] + [storage.raft] + dir = ["/data0/db/kvstore/"] + ``` + + 配置后，等待 TiFlash 会滚动重建结束。 + + 2. 升级 TiDB Operator + +## 新功能 + +- 添加新的 `spec.dnsPolicy` 字段，以支持配置 Pod 的 DNSPolicy ([#4420](https://github.com/pingcap/tidb-operator/pull/4420), [@handlerww](https://github.com/handlerww)) + +## Bug 修复 + +- 修复当没有手动设置 TiFlash 配置 `raft.kvstore_path` 或 `storage.raft.dir` 字段的情况下，使用 v1.3.0 和 v1.3.0-beta.1 版本 Operator 升级旧版本 TiFlash 到 v5.4.0 及以后版本后，TiFlash 会丢失数据的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) + +- 修复不配置 TiFlash 配置 `tmp_path` 字段无法使用 TiFlash 的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) diff --git a/zh/whats-new-in-v1.3.md b/zh/whats-new-in-v1.3.md index fa1df5c965..928777088e 100644 --- a/zh/whats-new-in-v1.3.md +++ b/zh/whats-new-in-v1.3.md @@ -20,6 +20,27 @@ TiDB Operator v1.3 引入了以下关键特性，从扩展性、易用性、安 1. 使用各组件配置 `baseImage` 与 `version` 替代当前使用的 `image` 字段，可以参考文档[部署配置](configure-a-tidb-cluster.md#版本)。 2. 升级 TiDB Operator。 +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，部署 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator 情况下，直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 Operator 执行升级操作。 + + 如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator，那么你需要执行以下操作来升级 TiFlash： + + 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + + 2. 升级 TiFlash + ## 滚动更新改动 - TiFlash（>= v5.4.0）默认配置优化。TiDB Operator v1.3.0-beta.1 及之后版本针对 TiFlash v5.4.0 及之后版本的默认配置进行了优化，如果使用 v1.2 版本 TiDB Operator 部署了 v5.4 及更新版本的 TiDB 集群，升级 TiDB Operator 到 v1.3.0-beta.1 及之后版本会导致 TiFlash 组件滚动更新。建议在升级 TiDB 集群到 v5.4.0 或更新版本之前，先升级 TiDB Operator 到 v1.3 及以上版本。 From fe0da7df159914a19b41d0dc0aa6a2c609f33563 Mon Sep 17 00:00:00 2001 From: Shiori Date: Tue, 22 Feb 2022 20:33:11 +0800 Subject: [PATCH 02/16] Apply suggestions from code review Co-authored-by: Ran Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com> --- zh/releases/release-1.3.0-beta.1.md | 4 ++-- zh/releases/release-1.3.0.md | 2 +- zh/releases/release-1.3.1.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/zh/releases/release-1.3.0-beta.1.md b/zh/releases/release-1.3.0-beta.1.md index 2ad3158494..56580814df 100644 --- a/zh/releases/release-1.3.0-beta.1.md +++ b/zh/releases/release-1.3.0-beta.1.md @@ -18,7 +18,7 @@ TiDB Operator 版本：1.3.0-beta.1 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，部署 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator 情况下，直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 Operator 执行升级操作。 - 如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator，那么你需要执行以下操作来升级 TiFlash： + 如果需要使用 v1.3.0-beta.1 版本的 TiDB Operator，那么你需要执行以下操作来升级 TiFlash 到 5.4.0： 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 @@ -35,7 +35,7 @@ TiDB Operator 版本：1.3.0-beta.1 dir = ["/data0/kvstore""] ``` - 2. 升级 TiFlash + 2. 升级 TiFlash。 ## 滚动升级改动 diff --git a/zh/releases/release-1.3.0.md b/zh/releases/release-1.3.0.md index 52b46e33e8..3552bdb38f 100644 --- a/zh/releases/release-1.3.0.md +++ b/zh/releases/release-1.3.0.md @@ -34,7 +34,7 @@ TiDB Operator 版本：1.3.0 dir = ["/data0/kvstore""] ``` - 2. 升级 TiFlash + 2. 升级 TiFlash。 ## 新功能 diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index 887eac573b..b7a4856cb6 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -12,7 +12,7 @@ TiDB Operator 版本：1.3.0 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 和 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 Operator，以防止 TiFlash 丢失数据： - 1. 如果 TidbCluster 定义中未配置 TiFlash 配置中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则添加 `storage.raft.dir` 字段。 + 1. 如果 TidbCluster 定义中**没有显式**配置 TiFlash 配置 `spec.tiflash.config.config` 中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则显式添加 `storage.raft.dir` 字段。 ```yaml spec: @@ -36,6 +36,6 @@ TiDB Operator 版本：1.3.0 ## Bug 修复 -- 修复当没有手动设置 TiFlash 配置 `raft.kvstore_path` 或 `storage.raft.dir` 字段的情况下，使用 v1.3.0 和 v1.3.0-beta.1 版本 Operator 升级旧版本 TiFlash 到 v5.4.0 及以后版本后，TiFlash 会丢失数据的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) +- 修复当没有显式设置 TiFlash 配置 `raft.kvstore_path` 或 `storage.raft.dir` 字段的情况下，使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 升级 TiFlash 到 v5.4.0 及以后版本后，TiFlash 丢失元数据的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) - 修复不配置 TiFlash 配置 `tmp_path` 字段无法使用 TiFlash 的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) From 536c6281edfd3dafe98a1f486051950d94a57f2e Mon Sep 17 00:00:00 2001 From: Shiori Date: Tue, 22 Feb 2022 20:51:01 +0800 Subject: [PATCH 03/16] optimize --- zh/releases/release-1.3.0-beta.1.md | 23 +++++++++++++++++++++-- zh/releases/release-1.3.0.md | 23 +++++++++++++++++++++-- zh/releases/release-1.3.1.md | 16 ++++++++-------- zh/whats-new-in-v1.3.md | 21 ++------------------- 4 files changed, 52 insertions(+), 31 deletions(-) diff --git a/zh/releases/release-1.3.0-beta.1.md b/zh/releases/release-1.3.0-beta.1.md index 56580814df..dbf23c9329 100644 --- a/zh/releases/release-1.3.0-beta.1.md +++ b/zh/releases/release-1.3.0-beta.1.md @@ -16,9 +16,9 @@ TiDB Operator 版本：1.3.0-beta.1 1. 在各组件的配置中，使用 `baseImage` 与 `version` 字段代替当前使用的 `image` 字段，可以参考文档[部署配置](../configure-a-tidb-cluster.md#版本)。 2. 升级 TiDB Operator。 -- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，部署 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator 情况下，直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 Operator 执行升级操作。 +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 - 如果需要使用 v1.3.0-beta.1 版本的 TiDB Operator，那么你需要执行以下操作来升级 TiFlash 到 5.4.0： + 如果需要使用 v1.3.0-beta.1 版本的 TiDB Operator，那么升级 TiFlash 到 v5.4.0 或者新部署 v5.4.0 TiFlash 之前，你需要执行以下操作： 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 @@ -31,12 +31,31 @@ TiDB Operator 版本：1.3.0-beta.1 # ... tmp_path = "/data0/tmp" [storage] + [storage.main] + dir = ["/data0/db"] [storage.raft] dir = ["/data0/kvstore""] ``` 2. 升级 TiFlash。 +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。TidbCluster 定义中的 TiFlash 配置必须包含 `tmp_path` 字段。 + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.main] + dir = ["/data0/db"] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + ## 滚动升级改动 - 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更，如果使用 v1.2 版本 TiDB Operator 部署了 v5.4 及更新版本的 TiDB 集群，升级 TiDB Operator 到 v1.3.0-beta.1 版本会导致 TiFlash 组件滚动更新。建议在升级 TiDB 集群到 v5.4.0 或更新版本之前，先升级 TiDB Operator 到 v1.3 及以上版本。 diff --git a/zh/releases/release-1.3.0.md b/zh/releases/release-1.3.0.md index 3552bdb38f..2a53a8c06f 100644 --- a/zh/releases/release-1.3.0.md +++ b/zh/releases/release-1.3.0.md @@ -15,9 +15,9 @@ TiDB Operator 版本：1.3.0 2. 添加新的 `spec.acrossK8s` 字段到 TidbCluster 定义，其值设置为 `true`。 3. 升级 TiDB Operator。 -- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，部署 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator 情况下，直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 Operator 执行升级操作。 +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 - 如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator，那么你需要执行以下操作来升级 TiFlash： + 如果需要使用 v1.3.0 版本的 TiDB Operator，那么升级 TiFlash 到 v5.4.0 之前，你需要执行以下操作： 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 @@ -30,12 +30,31 @@ TiDB Operator 版本：1.3.0 # ... tmp_path = "/data0/tmp" [storage] + [storage.main] + dir = ["/data0/db"] [storage.raft] dir = ["/data0/kvstore""] ``` 2. 升级 TiFlash。 +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。TidbCluster 定义中的 TiFlash 配置必须包含 `tmp_path` 字段。 + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.main] + dir = ["/data0/db"] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + ## 新功能 - 添加新的 `spec.tidb.tlsClient.skipInternalClientCA` 字段，以支持内部组件访问 TiDB 时跳过服务端证书验证 ([#4388](https://github.com/pingcap/tidb-operator/pull/4388), [@just1900](https://github.com/just1900)) diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index b7a4856cb6..5b6612f353 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -1,16 +1,16 @@ --- -title: TiDB Operator 1.3.0 Release Notes +title: TiDB Operator 1.3.1 Release Notes --- -# TiDB Operator 1.3.0 Release Notes +# TiDB Operator 1.3.1 Release Notes -发布日期: 2022 年 2 月 15 日 +发布日期: 2022 年 2 月 22 日 -TiDB Operator 版本：1.3.0 +TiDB Operator 版本：1.3.1 ## 兼容性改动 -- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 和 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 Operator，以防止 TiFlash 丢失数据： +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 Operator，以防止 TiFlash **丢失元数据**： 1. 如果 TidbCluster 定义中**没有显式**配置 TiFlash 配置 `spec.tiflash.config.config` 中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则显式添加 `storage.raft.dir` 字段。 @@ -26,9 +26,9 @@ TiDB Operator 版本：1.3.0 dir = ["/data0/db/kvstore/"] ``` - 配置后，等待 TiFlash 会滚动重建结束。 + 配置后，等待 TiFlash 滚动重建结束。 - 2. 升级 TiDB Operator + 2. 升级 TiDB Operator。 ## 新功能 @@ -38,4 +38,4 @@ TiDB Operator 版本：1.3.0 - 修复当没有显式设置 TiFlash 配置 `raft.kvstore_path` 或 `storage.raft.dir` 字段的情况下，使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 升级 TiFlash 到 v5.4.0 及以后版本后，TiFlash 丢失元数据的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) -- 修复不配置 TiFlash 配置 `tmp_path` 字段无法使用 TiFlash 的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) +- 修复 TiFlash 配置不包含 `tmp_path` 字段就无法使用 TiFlash 的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) diff --git a/zh/whats-new-in-v1.3.md b/zh/whats-new-in-v1.3.md index 928777088e..b9a579238c 100644 --- a/zh/whats-new-in-v1.3.md +++ b/zh/whats-new-in-v1.3.md @@ -20,26 +20,9 @@ TiDB Operator v1.3 引入了以下关键特性，从扩展性、易用性、安 1. 使用各组件配置 `baseImage` 与 `version` 替代当前使用的 `image` 字段，可以参考文档[部署配置](configure-a-tidb-cluster.md#版本)。 2. 升级 TiDB Operator。 -- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，部署 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator 情况下，直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 Operator 执行升级操作。 +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 - 如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator，那么你需要执行以下操作来升级 TiFlash： - - 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.raft] - dir = ["/data0/kvstore""] - ``` - - 2. 升级 TiFlash +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐使用 v1.3.1 及之后版本的 TiDB Operator 部署 TiFlash ## 滚动更新改动 From 48136f6876d035a2d38bae1907790c72a2ebc71b Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 10:23:21 +0800 Subject: [PATCH 04/16] add English notes --- en/TOC.md | 1 + en/releases/release-1.3.0-beta.1.md | 40 +++++++++++++++++++++++++++++ en/releases/release-1.3.0.md | 40 +++++++++++++++++++++++++++++ en/releases/release-1.3.1.md | 39 ++++++++++++++++++++++++++++ en/whats-new-in-v1.3.md | 4 +++ 5 files changed, 124 insertions(+) create mode 100644 en/releases/release-1.3.1.md diff --git a/en/TOC.md b/en/TOC.md index 2a7308edd6..d5ce109683 100644 --- a/en/TOC.md +++ b/en/TOC.md @@ -111,6 +111,7 @@ - [Monitoring and Alert on Kubernetes](monitor-kubernetes.md) - Release Notes - v1.3 + - [1.3.1](releases/release-1.3.1.md) - [1.3 GA](releases/release-1.3.0.md) - [1.3.0-beta.1](releases/release-1.3.0-beta.1.md) - v1.2 diff --git a/en/releases/release-1.3.0-beta.1.md b/en/releases/release-1.3.0-beta.1.md index cf55c59ab0..93113905b2 100644 --- a/en/releases/release-1.3.0-beta.1.md +++ b/en/releases/release-1.3.0-beta.1.md @@ -15,6 +15,46 @@ TiDB Operator version: 1.3.0-beta.1 1. Use the `baseImage` and `version` fields to replace the `image` field. For details, refer to [Configure TiDB deployment](../configure-a-tidb-cluster.md#version). 2. Upgrade TiDB Operator. +- Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0-beta.1 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. + + If you have to use v1.3.0-beta.1 TiDB Operator, you have to upgrade TiFlash to v5.4.0 by the following steps: + + 1. Check the config of TiFlash in TidbCluster spec, ensure `tmp_path` and `storage.raft.dir` (or `raft.kvstore_path`) fields existing. If these fields isn't existing, you need to add manually. + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.main] + dir = ["/data0/db"] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + + 2. Upgrade TiFlash. + +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0-beta.1 TiDB Operator. TiFlash's config in TidbCluster spec have to contain the `tmp_path` field. + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.main] + dir = ["/data0/db"] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + ## Rolling Update Changes - Due to changes in [#4358](https://github.com/pingcap/tidb-operator/pull/4358), if the TiDB cluster (>= v5.4) is deployed by TiDB Operator v1.2, upgrading TiDB Operator to v1.3.0-beta.1 causes TiFlash to rolling upgrade. It is recommended to upgrade TiDB Operator to v1.3 before upgrading the TiDB cluster to v5.4.0 or later versions. diff --git a/en/releases/release-1.3.0.md b/en/releases/release-1.3.0.md index 58c6eeb1ac..ab34a58b1c 100644 --- a/en/releases/release-1.3.0.md +++ b/en/releases/release-1.3.0.md @@ -15,6 +15,46 @@ TiDB Operator version: 1.3.0 2. Add a new `spec.acrossK8s` field in TidbCluster spec and set it to `true`. 3. Upgrade TiDB Operator. +- Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. + + If you have to use v1.3.0 TiDB Operator, you have to upgrade TiFlash to v5.4.0 by the following steps: + + 1. Check the config of TiFlash in TidbCluster spec, ensure `tmp_path` and `storage.raft.dir` (or `raft.kvstore_path`) fields existing. If these fields isn't existing, you need to add manually. + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.main] + dir = ["/data0/db"] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + + 2. Upgrade TiFlash. + +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 TiDB Operator. TiFlash's config in TidbCluster spec have to contain the `tmp_path` field. + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + tmp_path = "/data0/tmp" + [storage] + [storage.main] + dir = ["/data0/db"] + [storage.raft] + dir = ["/data0/kvstore""] + ``` + ## New Features - Add a new field `spec.tidb.tlsClient.skipInternalClientCA` to skip server certificate verification when internal components access TiDB ([#4388](https://github.com/pingcap/tidb-operator/pull/4388), [@just1900](https://github.com/just1900)) diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md new file mode 100644 index 0000000000..c9dcce514d --- /dev/null +++ b/en/releases/release-1.3.1.md @@ -0,0 +1,39 @@ +--- +title: TiDB Operator 1.3.1 Release Notes +--- + +# TiDB Operator 1.3.1 Release Notes + +Release date: February 22, 2022 + +TiDB Operator version: 1.3.1 + +## Compatibility Change + +- Due to issues [#4434](https://github.com/pingcap/tidb-operator/pull/4434) and [#4435](https://github.com/pingcap/tidb-operator/pull/4435), if you have deployed v5.4.0 version or later verion TiFlash when using v1.3.0 version or v1.3.0-beta.1 version TiDB Operator, you have to upgrade TiDB Operator by the following steps to **avoid TiFlash lose metadata**. + + 1. If there isn't `storage.rafe.dir` or `raft.kvstore_path` field of TiFlash's config `spec.tiflash.config.config` in TidbCluster spec, you need to add the `storage.raft.dir` field. + + ```yaml + spec: + # ... + tiflash: + config: + config: | + # ... + [storage] + [storage.raft] + dir = ["/data0/db/kvstore/"] + ``` + + 2. Upgrade TiDB Operator. + +## New Features + +- Add a new field `spec.dnsPolicy` to support configure `DNSPolicy` of Pod ([#4420](https://github.com/pingcap/tidb-operator/pull/4420), [@handlerww](https://github.com/handlerww)) + +## Bug fixes + +- Fix the issue that if you don't set `raft.kvstore_path` field or `storage.raft.dir` field in TiFlash's config, TiFlash will lose metadata after upgrading TiFlash to v5.4.0 or later when using v1.3.0 or v1.3.0-beta.1 TiDB Operator ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) + +- Fix the issue that can not use TiFlash if there isn't the `tmp_path` field in TiFlash's config ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) diff --git a/en/whats-new-in-v1.3.md b/en/whats-new-in-v1.3.md index bcc6ee066d..62ddf3f517 100644 --- a/en/whats-new-in-v1.3.md +++ b/en/whats-new-in-v1.3.md @@ -20,6 +20,10 @@ TiDB Operator 1.3 introduces the following key features, which helps you manage 1. Use fields `baseImage` and `version` to replace the field `image`, refer to the document [Configure TiDB deployment](configure-a-tidb-cluster.md#version). 2. Upgrade TiDB Operator. +- Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. + +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. + ## Rolling upgrade changes - Optimize the default configuration of TiFlash (>= v5.4.0). Since v1.3.0-beta.1, TiDB Operator optimizes the default configuration for TiFlash >= v5.4.0. If you deploy a TiDB cluster >= v5.4 using TiDB Operator v1.2, after upgrading TiDB Operator to v1.3.x, the TiFlash component will be rolling updated. It is recommended to upgrade TiDB Operator to v1.3.x before upgrading the TiDB cluster to v5.4.x. From 08c4d14deb1d1e2040d32eaed3569c99b1c2337f Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 11:02:32 +0800 Subject: [PATCH 05/16] Optimize --- en/releases/release-1.3.0-beta.1.md | 38 +---------------------------- en/releases/release-1.3.0.md | 38 +---------------------------- en/whats-new-in-v1.3.md | 2 +- zh/releases/release-1.3.0-beta.1.md | 38 +---------------------------- zh/releases/release-1.3.0.md | 38 +---------------------------- zh/whats-new-in-v1.3.md | 2 +- 6 files changed, 6 insertions(+), 150 deletions(-) diff --git a/en/releases/release-1.3.0-beta.1.md b/en/releases/release-1.3.0-beta.1.md index 93113905b2..09518f39f7 100644 --- a/en/releases/release-1.3.0-beta.1.md +++ b/en/releases/release-1.3.0-beta.1.md @@ -17,43 +17,7 @@ TiDB Operator version: 1.3.0-beta.1 - Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0-beta.1 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. - If you have to use v1.3.0-beta.1 TiDB Operator, you have to upgrade TiFlash to v5.4.0 by the following steps: - - 1. Check the config of TiFlash in TidbCluster spec, ensure `tmp_path` and `storage.raft.dir` (or `raft.kvstore_path`) fields existing. If these fields isn't existing, you need to add manually. - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` - - 2. Upgrade TiFlash. - -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0-beta.1 TiDB Operator. TiFlash's config in TidbCluster spec have to contain the `tmp_path` field. - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0-beta.1 TiDB Operator. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. ## Rolling Update Changes diff --git a/en/releases/release-1.3.0.md b/en/releases/release-1.3.0.md index ab34a58b1c..a3c4998873 100644 --- a/en/releases/release-1.3.0.md +++ b/en/releases/release-1.3.0.md @@ -17,43 +17,7 @@ TiDB Operator version: 1.3.0 - Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. - If you have to use v1.3.0 TiDB Operator, you have to upgrade TiFlash to v5.4.0 by the following steps: - - 1. Check the config of TiFlash in TidbCluster spec, ensure `tmp_path` and `storage.raft.dir` (or `raft.kvstore_path`) fields existing. If these fields isn't existing, you need to add manually. - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` - - 2. Upgrade TiFlash. - -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 TiDB Operator. TiFlash's config in TidbCluster spec have to contain the `tmp_path` field. - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 TiDB Operator. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. ## New Features diff --git a/en/whats-new-in-v1.3.md b/en/whats-new-in-v1.3.md index 62ddf3f517..77da86eb90 100644 --- a/en/whats-new-in-v1.3.md +++ b/en/whats-new-in-v1.3.md @@ -22,7 +22,7 @@ TiDB Operator 1.3 introduces the following key features, which helps you manage - Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, it's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. ## Rolling upgrade changes diff --git a/zh/releases/release-1.3.0-beta.1.md b/zh/releases/release-1.3.0-beta.1.md index dbf23c9329..82c92a951c 100644 --- a/zh/releases/release-1.3.0-beta.1.md +++ b/zh/releases/release-1.3.0-beta.1.md @@ -18,44 +18,8 @@ TiDB Operator 版本：1.3.0-beta.1 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 - 如果需要使用 v1.3.0-beta.1 版本的 TiDB Operator，那么升级 TiFlash 到 v5.4.0 或者新部署 v5.4.0 TiFlash 之前，你需要执行以下操作： - - 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` - - 2. 升级 TiFlash。 - -- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。TidbCluster 定义中的 TiFlash 配置必须包含 `tmp_path` 字段。 +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐升级到 v1.3.1 及之后版本后，再使用 TiFlash。 - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` - ## 滚动升级改动 - 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更，如果使用 v1.2 版本 TiDB Operator 部署了 v5.4 及更新版本的 TiDB 集群，升级 TiDB Operator 到 v1.3.0-beta.1 版本会导致 TiFlash 组件滚动更新。建议在升级 TiDB 集群到 v5.4.0 或更新版本之前，先升级 TiDB Operator 到 v1.3 及以上版本。 diff --git a/zh/releases/release-1.3.0.md b/zh/releases/release-1.3.0.md index 2a53a8c06f..0a0e581073 100644 --- a/zh/releases/release-1.3.0.md +++ b/zh/releases/release-1.3.0.md @@ -16,44 +16,8 @@ TiDB Operator 版本：1.3.0 3. 升级 TiDB Operator。 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 - - 如果需要使用 v1.3.0 版本的 TiDB Operator，那么升级 TiFlash 到 v5.4.0 之前，你需要执行以下操作： - - 1. 确认 TidbCluster 定义中的 TiFlash 配置，确保 `tmp_path` 和 `storage.raft.dir`（或 `raft.kvstore_path`）字段存在。如果字段不存在，那么需要手动添加。 - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` - - 2. 升级 TiFlash。 -- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。TidbCluster 定义中的 TiFlash 配置必须包含 `tmp_path` 字段。 - - ```yaml - spec: - # ... - tiflash: - config: - config: | - # ... - tmp_path = "/data0/tmp" - [storage] - [storage.main] - dir = ["/data0/db"] - [storage.raft] - dir = ["/data0/kvstore""] - ``` +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐升级到 v1.3.1 及之后版本后，再使用 TiFlash。 ## 新功能 diff --git a/zh/whats-new-in-v1.3.md b/zh/whats-new-in-v1.3.md index b9a579238c..ff0eb6d952 100644 --- a/zh/whats-new-in-v1.3.md +++ b/zh/whats-new-in-v1.3.md @@ -22,7 +22,7 @@ TiDB Operator v1.3 引入了以下关键特性，从扩展性、易用性、安 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 -- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐使用 v1.3.1 及之后版本的 TiDB Operator 部署 TiFlash +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐使用 v1.3.1 及之后版本的 TiDB Operator 使用 TiFlash。 ## 滚动更新改动 From ce8a08e55fb50213c862bf01d3dc0a857ccf513b Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 11:12:14 +0800 Subject: [PATCH 06/16] update --- en/releases/release-1.3.1.md | 4 ++++ zh/releases/release-1.3.1.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md index c9dcce514d..ce736e9398 100644 --- a/en/releases/release-1.3.1.md +++ b/en/releases/release-1.3.1.md @@ -32,6 +32,10 @@ TiDB Operator version: 1.3.1 - Add a new field `spec.dnsPolicy` to support configure `DNSPolicy` of Pod ([#4420](https://github.com/pingcap/tidb-operator/pull/4420), [@handlerww](https://github.com/handlerww)) +## Improvements + +- `tidb-lightning` Helm chart use `Local-backend` as default backend ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) + ## Bug fixes - Fix the issue that if you don't set `raft.kvstore_path` field or `storage.raft.dir` field in TiFlash's config, TiFlash will lose metadata after upgrading TiFlash to v5.4.0 or later when using v1.3.0 or v1.3.0-beta.1 TiDB Operator ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index 5b6612f353..615b2cf392 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -34,6 +34,10 @@ TiDB Operator 版本：1.3.1 - 添加新的 `spec.dnsPolicy` 字段，以支持配置 Pod 的 DNSPolicy ([#4420](https://github.com/pingcap/tidb-operator/pull/4420), [@handlerww](https://github.com/handlerww)) +## 优化提升 + +- `tidb-lightning` Helm chart 使用 `Local-backend` 后端作为默认后端 ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) + ## Bug 修复 - 修复当没有显式设置 TiFlash 配置 `raft.kvstore_path` 或 `storage.raft.dir` 字段的情况下，使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 升级 TiFlash 到 v5.4.0 及以后版本后，TiFlash 丢失元数据的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) From 7e22226b0d44a53bf1c6e5d6fb8417e63d24b32b Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 11:25:00 +0800 Subject: [PATCH 07/16] Apply suggestions from code review Co-authored-by: Ran Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com> --- en/releases/release-1.3.0-beta.1.md | 2 +- zh/releases/release-1.3.0-beta.1.md | 2 +- zh/releases/release-1.3.1.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/en/releases/release-1.3.0-beta.1.md b/en/releases/release-1.3.0-beta.1.md index 09518f39f7..51224353be 100644 --- a/en/releases/release-1.3.0-beta.1.md +++ b/en/releases/release-1.3.0-beta.1.md @@ -15,7 +15,7 @@ TiDB Operator version: 1.3.0-beta.1 1. Use the `baseImage` and `version` fields to replace the `image` field. For details, refer to [Configure TiDB deployment](../configure-a-tidb-cluster.md#version). 2. Upgrade TiDB Operator. -- Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0-beta.1 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. +- Due to the issue in [#4434](https://github.com/pingcap/tidb-operator/pull/4434), if you upgrade TiFlash to v5.4.0 or later when using v1.3.0-beta.1 TiDB Operator, TiFlash might lose metadata and not work. If TiFlash is deployed in your cluster, it is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before upgrading TiFlash. - Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0-beta.1 TiDB Operator. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. diff --git a/zh/releases/release-1.3.0-beta.1.md b/zh/releases/release-1.3.0-beta.1.md index 82c92a951c..c590201fbf 100644 --- a/zh/releases/release-1.3.0-beta.1.md +++ b/zh/releases/release-1.3.0-beta.1.md @@ -18,7 +18,7 @@ TiDB Operator 版本：1.3.0-beta.1 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 -- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐升级到 v1.3.1 及之后版本后，再使用 TiFlash。 +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下，必须在 TiFlash 的配置中显式配置 `tmp_path` 字段，才能使用 v5.4.0 及更高版本的 TiFlash。推荐升级到 v1.3.1 及之后版本后，再部署 TiFlash。 ## 滚动升级改动 diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index 615b2cf392..ed6ca65463 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -4,13 +4,13 @@ title: TiDB Operator 1.3.1 Release Notes # TiDB Operator 1.3.1 Release Notes -发布日期: 2022 年 2 月 22 日 +发布日期: 2022 年 2 月 23 日 TiDB Operator 版本：1.3.1 ## 兼容性改动 -- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 Operator，以防止 TiFlash **丢失元数据**： +- 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 TiDB Operator，以防止 TiFlash **丢失元数据**： 1. 如果 TidbCluster 定义中**没有显式**配置 TiFlash 配置 `spec.tiflash.config.config` 中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则显式添加 `storage.raft.dir` 字段。 From 38abccbbe6d9e8241441255805ba66df9280b6f5 Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 11:26:38 +0800 Subject: [PATCH 08/16] optmize --- en/releases/release-1.3.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md index ce736e9398..41378ba342 100644 --- a/en/releases/release-1.3.1.md +++ b/en/releases/release-1.3.1.md @@ -4,7 +4,7 @@ title: TiDB Operator 1.3.1 Release Notes # TiDB Operator 1.3.1 Release Notes -Release date: February 22, 2022 +Release date: February 23, 2022 TiDB Operator version: 1.3.1 From 6560bec6f625b5ff997878ab2de2d61dcc45e873 Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 11:29:45 +0800 Subject: [PATCH 09/16] optimize --- en/releases/release-1.3.1.md | 2 ++ zh/releases/release-1.3.1.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md index 41378ba342..ed2d5f6083 100644 --- a/en/releases/release-1.3.1.md +++ b/en/releases/release-1.3.1.md @@ -22,6 +22,8 @@ TiDB Operator version: 1.3.1 config: | # ... [storage] + [storage.main] + dir = ["/data0/db"] [storage.raft] dir = ["/data0/db/kvstore/"] ``` diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index ed6ca65463..3d90eb6ffa 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -22,6 +22,8 @@ TiDB Operator 版本：1.3.1 config: | # ... [storage] + [storage.main] + dir = ["/data0/db"] [storage.raft] dir = ["/data0/db/kvstore/"] ``` From 2bc95a8be3965e5a46402b3b0f230ddd934b2056 Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 11:45:24 +0800 Subject: [PATCH 10/16] optimize --- en/releases/release-1.3.0-beta.1.md | 2 +- en/releases/release-1.3.0.md | 2 +- en/whats-new-in-v1.3.md | 2 +- zh/releases/release-1.3.0.md | 2 +- zh/whats-new-in-v1.3.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/en/releases/release-1.3.0-beta.1.md b/en/releases/release-1.3.0-beta.1.md index 51224353be..0efd27bee9 100644 --- a/en/releases/release-1.3.0-beta.1.md +++ b/en/releases/release-1.3.0-beta.1.md @@ -17,7 +17,7 @@ TiDB Operator version: 1.3.0-beta.1 - Due to the issue in [#4434](https://github.com/pingcap/tidb-operator/pull/4434), if you upgrade TiFlash to v5.4.0 or later when using v1.3.0-beta.1 TiDB Operator, TiFlash might lose metadata and not work. If TiFlash is deployed in your cluster, it is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before upgrading TiFlash. -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0-beta.1 TiDB Operator. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using v1.3.0 TiDB Operator, you have to set `tmp_path` field in TiFlash's config to use v5.4.0 or later TiFlash. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. ## Rolling Update Changes diff --git a/en/releases/release-1.3.0.md b/en/releases/release-1.3.0.md index a3c4998873..66b13a53d9 100644 --- a/en/releases/release-1.3.0.md +++ b/en/releases/release-1.3.0.md @@ -17,7 +17,7 @@ TiDB Operator version: 1.3.0 - Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 TiDB Operator. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using v1.3.0 TiDB Operator, you have to set `tmp_path` field in TiFlash's config to use v5.4.0 or later TiFlash. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. ## New Features diff --git a/en/whats-new-in-v1.3.md b/en/whats-new-in-v1.3.md index 77da86eb90..a8e84925e6 100644 --- a/en/whats-new-in-v1.3.md +++ b/en/whats-new-in-v1.3.md @@ -22,7 +22,7 @@ TiDB Operator 1.3 introduces the following key features, which helps you manage - Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), If there isn't the `tmp_path` field in TiFlash's config, you can't use v5.4.0 TiFlash when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, it's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. +- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, you have to set `tmp_path` field in TiFlash's config to use v5.4.0 or later TiFlash. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. ## Rolling upgrade changes diff --git a/zh/releases/release-1.3.0.md b/zh/releases/release-1.3.0.md index 0a0e581073..510b4b864d 100644 --- a/zh/releases/release-1.3.0.md +++ b/zh/releases/release-1.3.0.md @@ -17,7 +17,7 @@ TiDB Operator 版本：1.3.0 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 -- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐升级到 v1.3.1 及之后版本后，再使用 TiFlash。 +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 版本的 TiDB Operator 情况下，必须在 TiFlash 的配置中显式配置 `tmp_path` 字段，才能使用 v5.4.0 及更高版本的 TiFlash。推荐升级到 v1.3.1 及之后版本后，再部署 TiFlash。 ## 新功能 diff --git a/zh/whats-new-in-v1.3.md b/zh/whats-new-in-v1.3.md index ff0eb6d952..a1f4901df8 100644 --- a/zh/whats-new-in-v1.3.md +++ b/zh/whats-new-in-v1.3.md @@ -22,7 +22,7 @@ TiDB Operator v1.3 引入了以下关键特性，从扩展性、易用性、安 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，直接升级 TiFlash 到 v5.4.0 及更高版本可能会导致 TiFlash **无法使用并且丢失元数据**。如果集群中部署了 TiFlash，推荐升级到 v1.3.1 及之后版本，再执行升级操作。 -- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，如果 TiFlash 的配置不包含 `tmp_path` 字段，则无法使用 v5.4.0 版本的 TiFlash。推荐使用 v1.3.1 及之后版本的 TiDB Operator 使用 TiFlash。 +- 由于 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，在部署 v1.3.0 或 v1.3.0-beta.1 版本的 TiDB Operator 情况下，必须在 TiFlash 的配置中显式配置 `tmp_path` 字段，才能使用 v5.4.0 及更高版本的 TiFlash。推荐升级到 v1.3.1 及之后版本后，再部署 TiFlash。 ## 滚动更新改动 From 1b247616bbcbd4923d4cc8417394c95f6ff3edc7 Mon Sep 17 00:00:00 2001 From: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com> Date: Wed, 23 Feb 2022 11:54:47 +0800 Subject: [PATCH 11/16] Apply suggestions from code review Co-authored-by: Ran --- zh/releases/release-1.3.1.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index 3d90eb6ffa..f584dd5f0f 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -28,7 +28,7 @@ TiDB Operator 版本：1.3.1 dir = ["/data0/db/kvstore/"] ``` - 配置后，等待 TiFlash 滚动重建结束。 + 配置后，等待 TiFlash 滚动更新结束。 2. 升级 TiDB Operator。 @@ -44,4 +44,4 @@ TiDB Operator 版本：1.3.1 - 修复当没有显式设置 TiFlash 配置 `raft.kvstore_path` 或 `storage.raft.dir` 字段的情况下，使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 升级 TiFlash 到 v5.4.0 及以后版本后，TiFlash 丢失元数据的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) -- 修复 TiFlash 配置不包含 `tmp_path` 字段就无法使用 TiFlash 的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) +- 修复 TiFlash 配置中缺少 `tmp_path` 字段时无法使用 TiFlash 的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) From aee2630f22767443ec4654c7fb5dce2d4a5e7344 Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 12:33:36 +0800 Subject: [PATCH 12/16] Apply suggestions from code review Co-authored-by: Ran Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com> --- en/releases/release-1.3.0-beta.1.md | 2 +- en/releases/release-1.3.0.md | 4 ++-- en/releases/release-1.3.1.md | 16 ++++++++-------- en/whats-new-in-v1.3.md | 4 ++-- zh/releases/release-1.3.1.md | 2 +- 5 files changed, 14 insertions(+), 14 deletions(-) diff --git a/en/releases/release-1.3.0-beta.1.md b/en/releases/release-1.3.0-beta.1.md index 0efd27bee9..b3271ce969 100644 --- a/en/releases/release-1.3.0-beta.1.md +++ b/en/releases/release-1.3.0-beta.1.md @@ -17,7 +17,7 @@ TiDB Operator version: 1.3.0-beta.1 - Due to the issue in [#4434](https://github.com/pingcap/tidb-operator/pull/4434), if you upgrade TiFlash to v5.4.0 or later when using v1.3.0-beta.1 TiDB Operator, TiFlash might lose metadata and not work. If TiFlash is deployed in your cluster, it is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before upgrading TiFlash. -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using v1.3.0 TiDB Operator, you have to set `tmp_path` field in TiFlash's config to use v5.4.0 or later TiFlash. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. +- Due to the issue in [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using TiDB Operator v1.3.0-beta.1, you must set the `tmp_path` field in TiFlash's config to use TiFlash v5.4.0 or later versions. It is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before you deploy TiFlash. ## Rolling Update Changes diff --git a/en/releases/release-1.3.0.md b/en/releases/release-1.3.0.md index 66b13a53d9..9c93f04715 100644 --- a/en/releases/release-1.3.0.md +++ b/en/releases/release-1.3.0.md @@ -15,9 +15,9 @@ TiDB Operator version: 1.3.0 2. Add a new `spec.acrossK8s` field in TidbCluster spec and set it to `true`. 3. Upgrade TiDB Operator. -- Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. +- Due to the issue in [#4434](https://github.com/pingcap/tidb-operator/pull/4434), if you upgrade TiFlash to v5.4.0 or later when using v1.3.0 TiDB Operator, TiFlash might lose metadata and not work. If TiFlash is deployed in your cluster, it is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before upgrading TiFlash. -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using v1.3.0 TiDB Operator, you have to set `tmp_path` field in TiFlash's config to use v5.4.0 or later TiFlash. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. +- Due to the issue in [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using TiDB Operator v1.3.0, you must set the `tmp_path` field in TiFlash's config to use TiFlash v5.4.0 or later versions. It is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before you deploy TiFlash. ## New Features diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md index ed2d5f6083..07c0c7d1af 100644 --- a/en/releases/release-1.3.1.md +++ b/en/releases/release-1.3.1.md @@ -10,9 +10,9 @@ TiDB Operator version: 1.3.1 ## Compatibility Change -- Due to issues [#4434](https://github.com/pingcap/tidb-operator/pull/4434) and [#4435](https://github.com/pingcap/tidb-operator/pull/4435), if you have deployed v5.4.0 version or later verion TiFlash when using v1.3.0 version or v1.3.0-beta.1 version TiDB Operator, you have to upgrade TiDB Operator by the following steps to **avoid TiFlash lose metadata**. +- Due to the issues in [#4434](https://github.com/pingcap/tidb-operator/pull/4434) and [#4435](https://github.com/pingcap/tidb-operator/pull/4435), if you have deployed TiFlash v5.4.0 or later versions when using TiDB Operator v1.3.0 or v1.3.0-beta.1, you must upgrade TiDB Operator by taking the following steps to **avoid TiFlash losing metadata**. - 1. If there isn't `storage.rafe.dir` or `raft.kvstore_path` field of TiFlash's config `spec.tiflash.config.config` in TidbCluster spec, you need to add the `storage.raft.dir` field. + 1. In TidbCluster spec, if the `storage.rafe.dir` and `raft.kvstore_path` fields in TiFlash's config `spec.tiflash.config.config` are not explicitly configured, you need to add the `storage.raft.dir` field. ```yaml spec: @@ -30,16 +30,16 @@ TiDB Operator version: 1.3.1 2. Upgrade TiDB Operator. -## New Features +## New Feature -- Add a new field `spec.dnsPolicy` to support configure `DNSPolicy` of Pod ([#4420](https://github.com/pingcap/tidb-operator/pull/4420), [@handlerww](https://github.com/handlerww)) +- Add a new field `spec.dnsPolicy` to support configuring `DNSPolicy` for Pods ([#4420](https://github.com/pingcap/tidb-operator/pull/4420), [@handlerww](https://github.com/handlerww)) -## Improvements +## Improvement -- `tidb-lightning` Helm chart use `Local-backend` as default backend ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) +- `tidb-lightning` Helm chart uses `Local-backend` as the default backend ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) ## Bug fixes -- Fix the issue that if you don't set `raft.kvstore_path` field or `storage.raft.dir` field in TiFlash's config, TiFlash will lose metadata after upgrading TiFlash to v5.4.0 or later when using v1.3.0 or v1.3.0-beta.1 TiDB Operator ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) +- Fix the issue that if the `raft.kvstore_path` field or the `storage.raft.dir` field is not set in TiFlash's config, TiFlash will lose metadata after upgrading TiFlash to v5.4.0 or later versions when using TiDB Operator v1.3.0 or v1.3.0-beta.1 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) -- Fix the issue that can not use TiFlash if there isn't the `tmp_path` field in TiFlash's config ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) +- Fix the issue that TiFlash does not work if the `tmp_path` field is not set in TiFlash's config ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) diff --git a/en/whats-new-in-v1.3.md b/en/whats-new-in-v1.3.md index a8e84925e6..0f7d99b124 100644 --- a/en/whats-new-in-v1.3.md +++ b/en/whats-new-in-v1.3.md @@ -20,9 +20,9 @@ TiDB Operator 1.3 introduces the following key features, which helps you manage 1. Use fields `baseImage` and `version` to replace the field `image`, refer to the document [Configure TiDB deployment](configure-a-tidb-cluster.md#version). 2. Upgrade TiDB Operator. -- Due to the issue [#4434](https://github.com/pingcap/tidb-operator/pull/4434), If you upgrade TiFlash to v5.4.0 or later when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, TiFlash maybe lose metadata and not work. If TiFlash is deployed in your cluster, it's recommended that upgrade TiDB Operator to v1.3.1 or later to upgrade TiFlash. +- Due to the issue in [#4434](https://github.com/pingcap/tidb-operator/pull/4434), if you upgrade TiFlash to v5.4.0 or later when using TiDB Operator v1.3.0-beta.1 or v1.3.0, TiFlash might lose metadata and not work. If TiFlash is deployed in your cluster, it is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before upgrading TiFlash. -- Due to the issue [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using v1.3.0 or v1.3.0-beta.1 TiDB Operator, you have to set `tmp_path` field in TiFlash's config to use v5.4.0 or later TiFlash. It's recommended that upgrade TiDB Operator to v1.3.1 or later to use TiFlash. +- Due to the issue in [#4435](https://github.com/pingcap/tidb-operator/pull/4435), when using TiDB Operator v1.3.0 or v1.3.0-beta.1, you must set the `tmp_path` field in TiFlash's config to use TiFlash v5.4.0 or later versions. It is recommended that you upgrade TiDB Operator to v1.3.1 or later versions before you deploy TiFlash. ## Rolling upgrade changes diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index f584dd5f0f..28da21eb1d 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -12,7 +12,7 @@ TiDB Operator 版本：1.3.1 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 TiDB Operator，以防止 TiFlash **丢失元数据**： - 1. 如果 TidbCluster 定义中**没有显式**配置 TiFlash 配置 `spec.tiflash.config.config` 中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则显式添加 `storage.raft.dir` 字段。 + 1. 如果 TidbCluster 定义中**没有显式**配置 TiFlash 配置 `spec.tiflash.config.config` 中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则显式添加 `storage.raft.dir` 字段。如果 `storage.main.dir` 没有显示配置，也需要显式添加。 ```yaml spec: From 88173f145a401332741519a7d4890def6673dea6 Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 13:49:46 +0800 Subject: [PATCH 13/16] Apply suggestions from code review Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com> --- zh/releases/release-1.3.1.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index 28da21eb1d..dda44e9e9b 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -38,10 +38,10 @@ TiDB Operator 版本：1.3.1 ## 优化提升 -- `tidb-lightning` Helm chart 使用 `Local-backend` 后端作为默认后端 ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) +- `tidb-lightning` Helm chart 使用 `local` backend 作为默认后端 ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) ## Bug 修复 - 修复当没有显式设置 TiFlash 配置 `raft.kvstore_path` 或 `storage.raft.dir` 字段的情况下，使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 升级 TiFlash 到 v5.4.0 及以后版本后，TiFlash 丢失元数据的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) -- 修复 TiFlash 配置中缺少 `tmp_path` 字段时无法使用 TiFlash 的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) +- 修复 TiFlash 配置中缺少 `tmp_path` 字段时，使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 无法使用 TiFlash v5.4.0 及以后版本的问题 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) From 7649a0c937b64a7284d86b6c5400ecc762fb68a2 Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 13:52:55 +0800 Subject: [PATCH 14/16] optimize --- en/releases/release-1.3.1.md | 4 ++-- zh/releases/release-1.3.1.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md index 07c0c7d1af..fd96e0b914 100644 --- a/en/releases/release-1.3.1.md +++ b/en/releases/release-1.3.1.md @@ -36,10 +36,10 @@ TiDB Operator version: 1.3.1 ## Improvement -- `tidb-lightning` Helm chart uses `Local-backend` as the default backend ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) +- `tidb-lightning` Helm chart uses `local` backend as the default backend ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) ## Bug fixes - Fix the issue that if the `raft.kvstore_path` field or the `storage.raft.dir` field is not set in TiFlash's config, TiFlash will lose metadata after upgrading TiFlash to v5.4.0 or later versions when using TiDB Operator v1.3.0 or v1.3.0-beta.1 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) -- Fix the issue that TiFlash does not work if the `tmp_path` field is not set in TiFlash's config ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) +- Fix the issue that TiFlash v5.4.0 or later versions does not work if the `tmp_path` field is not set in TiFlash's config when using TiDB Operator v1.3.0 or v1.3.0-beta.1 ([#4430](https://github.com/pingcap/tidb-operator/pull/4430), [@KanShiori](https://github.com/KanShiori)) diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index dda44e9e9b..e9e628f212 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -38,7 +38,7 @@ TiDB Operator 版本：1.3.1 ## 优化提升 -- `tidb-lightning` Helm chart 使用 `local` backend 作为默认后端 ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) +- `tidb-lightning` Helm chart 使用 `local` 后端作为默认后端 ([#4426](https://github.com/pingcap/tidb-operator/pull/4426), [@KanShiori](https://github.com/KanShiori)) ## Bug 修复 From b82ae2ca6b291a31385a4e2ebd4e72727798c3ab Mon Sep 17 00:00:00 2001 From: Shiori Date: Wed, 23 Feb 2022 14:11:30 +0800 Subject: [PATCH 15/16] Apply suggestions from code review Co-authored-by: Ran --- en/releases/release-1.3.1.md | 2 +- zh/releases/release-1.3.1.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md index fd96e0b914..460a117b93 100644 --- a/en/releases/release-1.3.1.md +++ b/en/releases/release-1.3.1.md @@ -12,7 +12,7 @@ TiDB Operator version: 1.3.1 - Due to the issues in [#4434](https://github.com/pingcap/tidb-operator/pull/4434) and [#4435](https://github.com/pingcap/tidb-operator/pull/4435), if you have deployed TiFlash v5.4.0 or later versions when using TiDB Operator v1.3.0 or v1.3.0-beta.1, you must upgrade TiDB Operator by taking the following steps to **avoid TiFlash losing metadata**. - 1. In TidbCluster spec, if the `storage.rafe.dir` and `raft.kvstore_path` fields in TiFlash's config `spec.tiflash.config.config` are not explicitly configured, you need to add the `storage.raft.dir` field. + 1. In TidbCluster spec, if the `storage.rafe.dir` and `raft.kvstore_path` fields in TiFlash's config `spec.tiflash.config.config` are not explicitly configured, you need to add the `storage.raft.dir` field. If `storage.main.dir` is not explicitly configured, you need to add the field. ```yaml spec: diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index e9e628f212..2566889dc2 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -12,7 +12,7 @@ TiDB Operator 版本：1.3.1 - 由于 [#4434](https://github.com/pingcap/tidb-operator/pull/4434) 和 [#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题，如果已经使用 v1.3.0 或者 v1.3.0-beta.1 版本 TiDB Operator 部署了 v5.4.0 及以后版本的 TiFlash，你需要执行以下步骤来升级 TiDB Operator，以防止 TiFlash **丢失元数据**： - 1. 如果 TidbCluster 定义中**没有显式**配置 TiFlash 配置 `spec.tiflash.config.config` 中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则显式添加 `storage.raft.dir` 字段。如果 `storage.main.dir` 没有显示配置，也需要显式添加。 + 1. 如果 TidbCluster 定义中**没有显式**配置 TiFlash 配置 `spec.tiflash.config.config` 中的 `storage.raft.dir` 和 `raft.kvstore_path` 字段，则显式添加 `storage.raft.dir` 字段。如果 `storage.main.dir` 没有显式配置，也需要显式添加。 ```yaml spec: From bd4024d69ceec0d53ffb79f9c441fc50c1f19a81 Mon Sep 17 00:00:00 2001 From: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com> Date: Thu, 24 Feb 2022 10:27:30 +0800 Subject: [PATCH 16/16] Apply suggestions from code review --- en/releases/release-1.3.1.md | 2 +- zh/releases/release-1.3.1.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/en/releases/release-1.3.1.md b/en/releases/release-1.3.1.md index 460a117b93..d8b5033aca 100644 --- a/en/releases/release-1.3.1.md +++ b/en/releases/release-1.3.1.md @@ -4,7 +4,7 @@ title: TiDB Operator 1.3.1 Release Notes # TiDB Operator 1.3.1 Release Notes -Release date: February 23, 2022 +Release date: February 24, 2022 TiDB Operator version: 1.3.1 diff --git a/zh/releases/release-1.3.1.md b/zh/releases/release-1.3.1.md index 2566889dc2..fc872c0045 100644 --- a/zh/releases/release-1.3.1.md +++ b/zh/releases/release-1.3.1.md @@ -4,7 +4,7 @@ title: TiDB Operator 1.3.1 Release Notes # TiDB Operator 1.3.1 Release Notes -发布日期: 2022 年 2 月 23 日 +发布日期: 2022 年 2 月 24 日 TiDB Operator 版本：1.3.1