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.

Sign up for GitHub

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.4.3 #10556

Merged
merged 3 commits into from
Oct 13, 2022
Merged

Bump version for v5.4.3 #10556

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9426543
Bump version for v5.4.3
Oreoxmt Sep 27, 2022
24bbb47
bum version
Oreoxmt Oct 12, 2022
ce65d52
Merge branch 'release-5.4' into bump/v5.4.3
Oreoxmt Oct 13, 2022
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
2 changes: 1 addition & 1 deletion check-before-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -695,7 +695,7 @@ sudo yum -y install numactl
1. Follow [Deploy a TiDB Cluster Using TiUP](/production-deployment-using-tiup.md) to deploy a cluster `tidb-test`. If you have installed a TiDB cluster, you can skip this step.

```bash
tiup cluster deploy tidb-test v6.1.0 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
tiup cluster deploy tidb-test v5.4.3 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
```

2. Run the `tiup cluster exec` command using the `sudo` privilege to install NUMA on all the target machines in the `tidb-test` cluster:
Expand Down
10 changes: 5 additions & 5 deletions download-ecosystem-tools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,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.4.2` is `https://download.pingcap.org/tidb-v5.4.2-linux-amd64.tar.gz`.
> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v5.4.3` is `https://download.pingcap.org/tidb-v5.4.3-linux-amd64.tar.gz`.

## TiDB Lightning

Expand All @@ -37,7 +37,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.4.2` is `https://download.pingcap.org/tidb-toolkit-v5.4.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.4.3` is `https://download.pingcap.org/tidb-toolkit-v5.4.3-linux-amd64.tar.gz`.

## BR (backup and restore)

Expand All @@ -49,7 +49,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.4.2` is `https://download.pingcap.org/tidb-toolkit-v5.4.2-linux-amd64.tar.gz`.
> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v5.4.3` is `https://download.pingcap.org/tidb-toolkit-v5.4.3-linux-amd64.tar.gz`.

## TiDB DM (Data Migration)

Expand All @@ -61,7 +61,7 @@ Download [DM](/dm/dm-overview.md) by using the download link in the following ta

> **Note:**
>
> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v5.4.2` is `https://download.pingcap.org/dm-v5.4.2-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.4.3` is `https://download.pingcap.org/dm-v5.4.3-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 @@ -73,7 +73,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.4.2` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.4.2-linux-amd64.tar.gz`. You can view the currently released versions in [TiDB Releases](https://github.com/pingcap/tidb/releases).
> The `{version}` in the download link is the version number of Dumpling. For example, the link for downloading the `v5.4.3` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.4.3-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
2 changes: 1 addition & 1 deletion pd-control.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ If you want to download the latest version of `pd-ctl`, directly download the Ti

> **Note:**
>
> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.4.2`, the package download link is `https://download.pingcap.org/tidb-v5.4.2-linux-amd64.tar.gz`.
> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.4.3`, the package download link is `https://download.pingcap.org/tidb-v5.4.3-linux-amd64.tar.gz`.

### Compile from source code

Expand Down
2 changes: 1 addition & 1 deletion pd-recover.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ To download the latest version of PD Recover, directly download the TiDB package

> **Note:**
>
> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.4.2`, the package download link is `https://download.pingcap.org/tidb-v5.4.2-linux-amd64.tar.gz`.
> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.4.3`, the package download link is `https://download.pingcap.org/tidb-v5.4.3-linux-amd64.tar.gz`.

## Quick Start

Expand Down
4 changes: 2 additions & 2 deletions production-deployment-using-tiup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -321,13 +321,13 @@ Before you run the `deploy` command, use the `check` and `check --apply` command
{{< copyable "shell-regular" >}}

```shell
tiup cluster deploy tidb-test v5.4.2 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
tiup cluster deploy tidb-test v5.4.3 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
```

In the `tiup cluster deploy` command above:

- `tidb-test` is the name of the TiDB cluster to be deployed.
- `v5.4.2` is the version of the TiDB cluster to be deployed. You can see the latest supported versions by running `tiup list tidb`.
- `v5.4.3` is the version of the TiDB cluster to be deployed. You can see the latest supported versions by running `tiup list tidb`.
- `topology.yaml` is the initialization configuration file.
- `--user root` indicates logging into the target machine as the `root` user to complete the cluster deployment. The `root` user is expected to have `ssh` and `sudo` privileges to the target machine. Alternatively, you can use other users with `ssh` and `sudo` privileges to complete the deployment.
- `[-i]` and `[-p]` are optional. If you have configured login to the target machine without password, these parameters are not required. If not, choose one of the two parameters. `[-i]` is the private key of the root user (or other users specified by `--user`) that has access to the target machine. `[-p]` is used to input the user password interactively.
Expand Down
8 changes: 4 additions & 4 deletions quick-start-with-tidb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,10 +80,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
{{< copyable "shell-regular" >}}

```shell
tiup playground v5.4.2 --db 2 --pd 3 --kv 3
tiup playground v5.4.3 --db 2 --pd 3 --kv 3
```

The command downloads a version cluster to the local machine and starts it, such as v5.4.2. To view the latest version, run `tiup list tidb`.
The command downloads a version cluster to the local machine and starts it, such as v5.4.3. To view the latest version, run `tiup list tidb`.

This command returns the access methods of the cluster:

Expand Down Expand Up @@ -201,10 +201,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
{{< copyable "shell-regular" >}}

```shell
tiup playground v5.4.2 --db 2 --pd 3 --kv 3
tiup playground v5.4.3 --db 2 --pd 3 --kv 3
```

The command downloads a version cluster to the local machine and starts it, such as v5.4.2. To view the latest version, run `tiup list tidb`.
The command downloads a version cluster to the local machine and starts it, such as v5.4.3. To view the latest version, run `tiup list tidb`.

This command returns the access methods of the cluster:

Expand Down
2 changes: 1 addition & 1 deletion scale-tidb-using-tiup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,7 +275,7 @@ This section exemplifies how to remove a TiKV node from the `10.0.1.5` host.
```
Starting /root/.tiup/components/cluster/v1.9.0/cluster display <cluster-name>
TiDB Cluster: <cluster-name>
TiDB Version: v5.4.2
TiDB Version: v5.4.3
ID Role Host Ports Status Data Dir Deploy Dir
-- ---- ---- ----- ------ -------- ----------
10.0.1.3:8300 cdc 10.0.1.3 8300 Up data/cdc-8300 deploy/cdc-8300
Expand Down
2 changes: 1 addition & 1 deletion sync-diff-inspector/sync-diff-inspector-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ summary: Use sync-diff-inspector to compare data and repair inconsistent data.

This guide introduces the key features of sync-diff-inspector and describes how to configure and use this tool. To download sync-diff-inspector, use one of the following methods:

+ Binary package. Click [tidb-community-toolkit-v5.4.2-linux-amd64](https://download.pingcap.org/tidb-community-toolkit-v5.4.2-linux-amd64.tar.gz) to download.
+ Binary package. Click [tidb-community-toolkit-v5.4.3-linux-amd64](https://download.pingcap.org/tidb-community-toolkit-v5.4.3-linux-amd64.tar.gz) to download.
+ Docker image. Execute the following command to download:

{{< copyable "shell-regular" >}}
Expand Down
4 changes: 2 additions & 2 deletions ticdc/manage-ticdc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,14 +11,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.4.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.4.3.

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

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

### Notes for upgrade
Expand Down
24 changes: 12 additions & 12 deletions tiup/tiup-cluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,20 +112,20 @@ tidb_servers:
...
```

Save the file as `/tmp/topology.yaml`. If you want to use TiDB v5.4.2 and your cluster name is `prod-cluster`, run the following command:
Save the file as `/tmp/topology.yaml`. If you want to use TiDB v5.4.3 and your cluster name is `prod-cluster`, run the following command:

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

```shell
tiup cluster deploy -p prod-cluster v5.4.2 /tmp/topology.yaml
tiup cluster deploy -p prod-cluster v5.4.3 /tmp/topology.yaml
```

During the execution, TiUP asks you to confirm your topology again and requires the root password of the target machine (the `-p` flag means inputting password):

```bash
Please confirm your topology:
TiDB Cluster: prod-cluster
TiDB Version: v5.4.2
TiDB Version: v5.4.3
Type Host Ports Directories
---- ---- ----- -----------
pd 172.16.5.134 2379/2380 deploy/pd-2379,data/pd-2379
Expand Down Expand Up @@ -165,7 +165,7 @@ tiup cluster list
Starting /root/.tiup/components/cluster/v1.9.0/cluster list
Name User Version Path PrivateKey
---- ---- ------- ---- ----------
prod-cluster tidb v5.4.2 /root/.tiup/storage/cluster/clusters/prod-cluster /root/.tiup/storage/cluster/clusters/prod-cluster/ssh/id_rsa
prod-cluster tidb v5.4.3 /root/.tiup/storage/cluster/clusters/prod-cluster /root/.tiup/storage/cluster/clusters/prod-cluster/ssh/id_rsa
```

## Start the cluster
Expand Down Expand Up @@ -193,7 +193,7 @@ tiup cluster display prod-cluster
```
Starting /root/.tiup/components/cluster/v1.9.0/cluster display prod-cluster
TiDB Cluster: prod-cluster
TiDB Version: v5.4.2
TiDB Version: v5.4.3
ID Role Host Ports Status Data Dir Deploy Dir
-- ---- ---- ----- ------ -------- ----------
172.16.5.134:3000 grafana 172.16.5.134 3000 Up - deploy/grafana-3000
Expand Down Expand Up @@ -264,7 +264,7 @@ tiup cluster display prod-cluster
```
Starting /root/.tiup/components/cluster/v1.9.0/cluster display prod-cluster
TiDB Cluster: prod-cluster
TiDB Version: v5.4.2
TiDB Version: v5.4.3
ID Role Host Ports Status Data Dir Deploy Dir
-- ---- ---- ----- ------ -------- ----------
172.16.5.134:3000 grafana 172.16.5.134 3000 Up - deploy/grafana-3000
Expand Down Expand Up @@ -372,12 +372,12 @@ Global Flags:
-y, --yes Skip all confirmations and assumes 'yes'
```

For example, the following command upgrades the cluster to v5.4.2:
For example, the following command upgrades the cluster to v5.4.3:

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

```bash
tiup cluster upgrade tidb-test v5.4.2
tiup cluster upgrade tidb-test v5.4.3
```

## Update configuration
Expand Down Expand Up @@ -559,11 +559,11 @@ tiup cluster audit
Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.9.0/cluster audit
ID Time Command
-- ---- -------
4BLhr0 2022-07-08T13:25:09+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.2 /tmp/topology.yaml
4BKWjF 2022-07-08T23:36:57+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.2 /tmp/topology.yaml
4BKVwH 2022-07-08T23:02:08+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.2 /tmp/topology.yaml
4BLhr0 2022-07-08T13:25:09+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.3 /tmp/topology.yaml
4BKWjF 2022-07-08T23:36:57+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.3 /tmp/topology.yaml
4BKVwH 2022-07-08T23:02:08+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.3 /tmp/topology.yaml
4BKKH1 2022-07-08T16:39:04+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster destroy test
4BKKDx 2022-07-08T16:36:57+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.2 /tmp/topology.yaml
4BKKDx 2022-07-08T16:36:57+08:00 /home/tidb/.tiup/components/cluster/v1.9.0/cluster deploy test v5.4.3 /tmp/topology.yaml
```

The first column is `audit-id`. To view the execution log of a certain command, pass the `audit-id` of a command as the flag as follows:
Expand Down
2 changes: 1 addition & 1 deletion tiup/tiup-component-cluster-deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ tiup cluster deploy <cluster-name> <version> <topology.yaml> [flags]
```

- `<cluster-name>`: the name of the new cluster, which cannot be the same as the existing cluster names.
- `<version>`: the version number of the TiDB cluster to deploy, such as `v5.4.2`.
- `<version>`: the version number of the TiDB cluster to deploy, such as `v5.4.3`.
- `<topology.yaml>`: the prepared [topology file](/tiup/tiup-cluster-topology-reference.md).

## Options
Expand Down
12 changes: 6 additions & 6 deletions tiup/tiup-component-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,12 +69,12 @@ Example 2: Use TiUP to install the nightly version of TiDB.
tiup install tidb:nightly
```

Example 3: Use TiUP to install TiKV v5.4.2.
Example 3: Use TiUP to install TiKV v5.4.3.

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

```shell
tiup install tikv:v5.4.2
tiup install tikv:v5.4.3
```

## Upgrade components
Expand Down Expand Up @@ -127,12 +127,12 @@ Before the component is started, TiUP creates a directory for it, and then puts

If you want to start the same component multiple times and reuse the previous working directory, you can use `--tag` to specify the same name when the component is started. After the tag is specified, the working directory will *not be automatically deleted* when the instance is terminated, which makes it convenient to reuse the working directory.

Example 1: Operate TiDB v5.4.2.
Example 1: Operate TiDB v5.4.3.

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

```shell
tiup tidb:v5.4.2
tiup tidb:v5.4.3
```

Example 2: Specify the tag with which TiKV operates.
Expand Down Expand Up @@ -218,12 +218,12 @@ The following flags are supported in this command:
- If the version is ignored, adding `--all` means to uninstall all versions of this component.
- If the version and the component are both ignored, adding `--all` means to uninstall all components of all versions.

Example 1: Uninstall TiDB v5.4.2.
Example 1: Uninstall TiDB v5.4.3.

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

```shell
tiup uninstall tidb:v5.4.2
tiup uninstall tidb:v5.4.3
```

Example 2: Uninstall TiKV of all versions.
Expand Down
6 changes: 3 additions & 3 deletions tiup/tiup-mirror.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,9 +87,9 @@ The `tiup mirror clone` command provides many optional flags (might provide more

If you want to clone only one version (not all versions) of a component, use `--<component>=<version>` to specify this version. For example:

- Execute the `tiup mirror clone <target-dir> --tidb v5.4.2` command to clone the v5.4.2 version of the TiDB component.
- Run the `tiup mirror clone <target-dir> --tidb v5.4.2 --tikv all` command to clone the v5.4.2 version of the TiDB component and all versions of the TiKV component.
- Run the `tiup mirror clone <target-dir> v5.4.2` command to clone the v5.4.2 version of all components in a cluster.
- Execute the `tiup mirror clone <target-dir> --tidb v5.4.3` command to clone the v5.4.3 version of the TiDB component.
- Run the `tiup mirror clone <target-dir> --tidb v5.4.3 --tikv all` command to clone the v5.4.3 version of the TiDB component and all versions of the TiKV component.
- Run the `tiup mirror clone <target-dir> v5.4.3` command to clone the v5.4.3 version of all components in a cluster.

After cloning, signing keys are set up automatically.

Expand Down
2 changes: 1 addition & 1 deletion tiup/tiup-playground.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ This command actually performs the following operations:

- Because this command does not specify the version of the playground component, TiUP first checks the latest version of the installed playground component. Assume that the latest version is v1.9.0, then this command works the same as `tiup playground:v1.9.0`.
- If you have not used TiUP playground to install the TiDB, TiKV, and PD components, the playground component installs the latest stable version of these components, and then start these instances.
- Because this command does not specify the version of the TiDB, PD, and TiKV component, TiUP playground uses the latest version of each component by default. Assume that the latest version is v5.4.2, then this command works the same as `tiup playground:v1.9.0 v5.4.2`.
- Because this command does not specify the version of the TiDB, PD, and TiKV component, TiUP playground uses the latest version of each component by default. Assume that the latest version is v5.4.3, then this command works the same as `tiup playground:v1.9.0 v5.4.3`.
- Because this command does not specify the number of each component, TiUP playground, by default, starts a smallest cluster that consists of one TiDB instance, one TiKV instance, one PD instance, and one TiFlash instance.
- After starting each TiDB component, TiUP playground reminds you that the cluster is successfully started and provides you some useful information, such as how to connect to the TiDB cluster through the MySQL client and how to access the [TiDB Dashboard](/dashboard/dashboard-intro.md).

Expand Down
8 changes: 4 additions & 4 deletions upgrade-tidb-using-tiup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,12 +161,12 @@ If your application has a maintenance window for the database to be stopped for
tiup cluster upgrade <cluster-name> <version>
```

For example, if you want to upgrade the cluster to v5.4.2:
For example, if you want to upgrade the cluster to v5.4.3:

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

```shell
tiup cluster upgrade <cluster-name> v5.4.2
tiup cluster upgrade <cluster-name> v5.4.3
```

> **Note:**
Expand Down Expand Up @@ -221,7 +221,7 @@ tiup cluster display <cluster-name>
```
Cluster type: tidb
Cluster name: <cluster-name>
Cluster version: v5.4.2
Cluster version: v5.4.3
```

> **Note:**
Expand Down Expand Up @@ -271,7 +271,7 @@ You can upgrade the tool version by using TiUP to install the `ctl` component of
{{< copyable "shell-regular" >}}

```shell
tiup install ctl:v5.4.2
tiup install ctl:v5.4.3
```

## TiDB 5.4 compatibility changes
Expand Down