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

Bump version for v5.3.0 - ecosystem tools #6830

Merged
merged 4 commits into from
Nov 24, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions download-ecosystem-tools.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ If you want to download the latest version of [TiDB Binlog](/tidb-binlog/tidb-bi

> **Note:**
>
> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v5.2.2` is `https://download.pingcap.org/tidb-v5.2.2-linux-amd64.tar.gz`.
> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v5.3.0` is `https://download.pingcap.org/tidb-v5.3.0-linux-amd64.tar.gz`.

## TiDB Lightning

Expand All @@ -30,7 +30,7 @@ Download [TiDB Lightning](/tidb-lightning/tidb-lightning-overview.md) by using t

> **Note:**
>
> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v5.2.2` is `https://download.pingcap.org/tidb-toolkit-v5.2.2-linux-amd64.tar.gz`.
> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v5.3.0` is `https://download.pingcap.org/tidb-toolkit-v5.3.0-linux-amd64.tar.gz`.

## BR (backup and restore)

Expand All @@ -42,7 +42,7 @@ Download [BR](/br/backup-and-restore-tool.md) by using the download link in the

> **Note:**
>
> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v5.2.2` is `https://download.pingcap.org/tidb-toolkit-v5.2.2-linux-amd64.tar.gz`.
> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v5.3.0` is `https://download.pingcap.org/tidb-toolkit-v5.3.0-linux-amd64.tar.gz`.

## TiDB DM (Data Migration)

Expand All @@ -54,7 +54,7 @@ Download [DM](https://docs.pingcap.com/tidb-data-migration/stable/overview) by u

> **Note:**
>
> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v2.0.6` is `https://download.pingcap.org/dm-v2.0.6-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page.
> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v5.3.0` is `https://download.pingcap.org/dm-v5.3.0-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page.

## Dumpling

Expand All @@ -66,7 +66,7 @@ Download [Dumpling](/dumpling-overview.md) from the links below:

> **Note:**
>
> The `{version}` in the download link is the version number of Dumpling. For example, the link for downloading the `v5.2.2` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.2.2-linux-amd64.tar.gz`. You can view the currently released versions in [Dumpling Releases](https://github.com/pingcap/dumpling/releases).
> The `{version}` in the download link is the version number of Dumpling. For example, the link for downloading the `v5.3.0` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.3.0-linux-amd64.tar.gz`. You can view the currently released versions in [TiDB Releases](https://github.com/pingcap/tidb/releases).
>
> Dumpling supports arm64 linux. You can replace `amd64` in the download link with `arm64`, which means the `arm64` version of Dumpling.

Expand Down
4 changes: 2 additions & 2 deletions ticdc/manage-ticdc.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,14 @@ You can also use the HTTP interface (the TiCDC OpenAPI feature) to manage the Ti

## Upgrade TiCDC using TiUP

This section introduces how to upgrade the TiCDC cluster using TiUP. In the following example, assume that you need to upgrade TiCDC and the entire TiDB cluster to v5.2.2.
This section introduces how to upgrade the TiCDC cluster using TiUP. In the following example, assume that you need to upgrade TiCDC and the entire TiDB cluster to v5.3.0.

{{< copyable "shell-regular" >}}

```shell
tiup update --self && \
tiup update --all && \
tiup cluster upgrade <cluster-name> v5.2.2
tiup cluster upgrade <cluster-name> v5.3.0
```

### Notes for upgrade
Expand Down
2 changes: 1 addition & 1 deletion tiup/tiup-component-dm-import.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ In DM v1.0, the cluster is basically deployed using TiDB Ansible. TiUP DM provid
> - Before importing the cluster, stop running the original cluster first.
> - For data migration tasks that need to be upgraded to v2.0, do not execute `stop-task` on these tasks.
> - The command only supports importing to DM v2.0.0-rc.2 and later versions.
> - The `import` command is used to import a DM v1.0 cluster to a new DM v2.0 cluster. If you need to import data migration tasks to an existing v2.0 cluster, refer to [Manually Upgrade TiDB Data Migration from v1.0.x to v2.0.x](https://docs.pingcap.com/tidb-data-migration/stable/manually-upgrade-dm-1.0-to-2.0)
> - The `import` command is used to import a DM v1.0 cluster to a new DM v2.0 cluster. If you need to import data migration tasks to an existing v2.0 cluster, refer to [Manually Upgrade TiDB Data Migration from v1.0.x to v2.0+](https://docs.pingcap.com/tidb-data-migration/stable/manually-upgrade-dm-1.0-to-2.0)
> - The deployment directories of some components might be different from those in the original cluster. You can check it with the `display` command.
> - Before importing the cluster, run `tiup update --self && tiup update dm` to upgrade TiUP DM components to the latest version.
> - After the cluster is imported, there is only one DM-master node in the cluster. You can refer to [the `scale out` command](/tiup/tiup-component-dm-scale-out.md) to scale out the DM-master node.
Expand Down