Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

en, zh: add release notes for v1.3.1 #1694

Merged
merged 16 commits into from
Feb 24, 2022
Merged

Conversation

KanShiori
Copy link
Contributor

What is changed, added, or deleted? (Required)

Which TiDB Operator version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v1.3 (TiDB Operator 1.3 versions)
  • v1.2 (TiDB Operator 1.2 versions)
  • v1.1 (TiDB Operator 1.1 versions)
  • v1.0 (TiDB Operator 1.0 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Feb 22, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • DanielZhangQD
  • ran-huang

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot requested a review from ran-huang February 22, 2022 09:51
@ti-chi-bot ti-chi-bot added missing-translation-status This PR does not have translation status info. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 22, 2022
@@ -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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

下面这段就不要了把,就不让用户用 这个 beta.1 版本了把,@ran-huang 觉得呢

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@@ -0,0 +1,41 @@
---
title: TiDB Operator 1.3.0 Release Notes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

版本没改

Comment on lines 32 to 34
[storage]
[storage.raft]
dir = ["/data0/kvstore""]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
[storage]
[storage.raft]
dir = ["/data0/kvstore""]
[storage]
[storage.main]
dir = ["/data0/db"]
[storage.raft]
dir = ["/data0/kvstore""]


## 兼容性改动

- 由于 [#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 丢失数据:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 [#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 丢失数据:

@@ -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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这段也不要了把,cc @ran-huang

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@@ -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 执行升级操作。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 [#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)[#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题,在部署 v1.3.0-beta.1 版本的 TiDB Operator 情况下,直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash **无法使用并且丢失数据**。推荐使用 v1.3.1 及之后版本的 TiDB Operator 执行升级操作。

zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved

如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator,那么你需要执行以下操作来升级 TiFlash:

1. 确认 TidbCluster 定义中的 TiFlash 配置,确保 `tmp_path` 和 `storage.raft.dir`(或 `raft.kvstore_path`)字段存在。如果字段不存在,那么需要手动添加。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

需要给 raft.kvstore_path 也放个例子吗?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这个是旧版本的配置,感觉不需要

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这一段不是要不要了吗?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这里不要,1.3.0 里面要吗?那这里就写 1.3.1 及之后了?

@@ -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 执行升级操作。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 [#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)[#4435](https://github.com/pingcap/tidb-operator/pull/4435) 的问题,部署 v1.3.0 版本的 TiDB Operator 情况下,直接升级 TiFlash 到 v5.4.0 版本可能会导致 TiFlash 无法使用并且丢失数据。推荐使用 v1.3.1 及之后版本 TiDB Operator 执行升级操作。

@@ -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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
如果需要使用 v1.3.0 或者 v1.3.0-beta.1 版本的 Operator,那么你需要执行以下操作来升级 TiFlash:
如果需要使用 v1.3.0 的 TiDB Operator,那么你需要执行以下操作来升级 TiFlash 到 5.4.0

zh/releases/release-1.3.0.md Outdated Show resolved Hide resolved

# TiDB Operator 1.3.0 Release Notes

发布日期: 2022 年 2 月 15 日
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

日期没改


- 修复当没有手动设置 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))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这两个“配置”有点读不通...

KanShiori and others added 2 commits February 22, 2022 20:33
Co-authored-by: Ran <huangran@pingcap.com>
Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com>
en/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.0.md Outdated Show resolved Hide resolved
en/releases/release-1.3.0.md Outdated Show resolved Hide resolved
en/whats-new-in-v1.3.md Outdated Show resolved Hide resolved
en/whats-new-in-v1.3.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
Co-authored-by: Ran <huangran@pingcap.com>
Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com>
KanShiori and others added 2 commits February 23, 2022 13:49
Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com>
Copy link
Contributor

@DanielZhangQD DanielZhangQD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Feb 23, 2022
Copy link
Contributor

@ran-huang ran-huang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

zh/releases/release-1.3.1.md Outdated Show resolved Hide resolved
en/releases/release-1.3.1.md Outdated Show resolved Hide resolved
Co-authored-by: Ran <huangran@pingcap.com>
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Feb 23, 2022
@ran-huang ran-huang added needs-cherry-pick-release-1.3 Should cherry pick this PR to release-1.3 branch. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. labels Feb 23, 2022
@ti-chi-bot ti-chi-bot removed the missing-translation-status This PR does not have translation status info. label Feb 23, 2022
@ran-huang
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: bd4024d

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Feb 24, 2022
@ran-huang ran-huang closed this Feb 24, 2022
@ran-huang ran-huang reopened this Feb 24, 2022
@ti-chi-bot ti-chi-bot merged commit aa0b674 into pingcap:master Feb 24, 2022
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created: #1698.

@KanShiori KanShiori deleted the rn_1.3.1 branch February 24, 2022 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-release-1.3 Should cherry pick this PR to release-1.3 branch. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants