bump version for v6.1.7 (#14165)

br/backup-and-restore-use-cases.md

@@ -39,10 +39,10 @@ It is recommended that you deploy the TiDB cluster using [TiUP](/tiup/tiup-clust
 
 ### Cluster versions
 
-- TiDB: v6.1.6
-- TiKV: v6.1.6
-- PD: v6.1.6
-- BR: v6.1.6
+- TiDB: v6.1.7
+- TiKV: v6.1.7
+- PD: v6.1.7
+- BR: v6.1.7
 
 > **Note:**
 >

check-before-deployment.md

@@ -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.6 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
+    tiup cluster deploy tidb-test v6.1.7 ./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:

dm/quick-start-create-task.md

@@ -73,7 +73,7 @@ To run a TiDB server, use the following command:
 {{< copyable "shell-regular" >}}
 
 ```bash
-wget https://download.pingcap.org/tidb-community-server-v6.1.6-linux-amd64.tar.gz
+wget https://download.pingcap.org/tidb-community-server-v6.1.7-linux-amd64.tar.gz
 tar -xzvf tidb-latest-linux-amd64.tar.gz
 mv tidb-latest-linux-amd64/bin/tidb-server ./
 ./tidb-server

download-ecosystem-tools.md

@@ -27,7 +27,7 @@ You can download TiDB Toolkit from the following link:
 https://download.pingcap.org/tidb-community-toolkit-{version}-linux-amd64.tar.gz
 ```
 
-`{version}` in the link indicates the version number of TiDB. For example, the download link for `v6.1.6` is `https://download.pingcap.org/tidb-community-toolkit-v6.1.6-linux-amd64.tar.gz`.
+`{version}` in the link indicates the version number of TiDB. For example, the download link for `v6.1.7` is `https://download.pingcap.org/tidb-community-toolkit-v6.1.7-linux-amd64.tar.gz`.
 
 > **Note:**
 >

pd-control.md

@@ -27,7 +27,7 @@ To obtain `pd-ctl` of the latest version, download the TiDB server installation
 
 > **Note:**
 >
-> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v6.1.6`, the package download link is `https://download.pingcap.org/tidb-community-server-v6.1.6-linux-amd64.tar.gz`.
+> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v6.1.7`, the package download link is `https://download.pingcap.org/tidb-community-server-v6.1.7-linux-amd64.tar.gz`.
 
 ### Compile from source code
 

production-deployment-using-tiup.md

@@ -333,13 +333,13 @@ Before you run the `deploy` command, use the `check` and `check --apply` command
     {{< copyable "shell-regular" >}}
 
     ```shell
-    tiup cluster deploy tidb-test v6.1.6 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
+    tiup cluster deploy tidb-test v6.1.7 ./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.
-- `v6.1.6` is the version of the TiDB cluster to be deployed. You can see the latest supported versions by running `tiup list tidb`.
+- `v6.1.7` 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.

quick-start-with-tidb.md

@@ -78,10 +78,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
         {{< copyable "shell-regular" >}}
 
         ```shell
-        tiup playground v6.1.6 --db 2 --pd 3 --kv 3
+        tiup playground v6.1.7 --db 2 --pd 3 --kv 3
         ```
 
-        The command downloads a version cluster to the local machine and starts it, such as v6.1.6. To view the latest version, run `tiup list tidb`.
+        The command downloads a version cluster to the local machine and starts it, such as v6.1.7. To view the latest version, run `tiup list tidb`.
 
         This command returns the access methods of the cluster:
 
@@ -199,10 +199,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
         {{< copyable "shell-regular" >}}
 
         ```shell
-        tiup playground v6.1.6 --db 2 --pd 3 --kv 3
+        tiup playground v6.1.7 --db 2 --pd 3 --kv 3
         ```
 
-        The command downloads a version cluster to the local machine and starts it, such as v6.1.6. To view the latest version, run `tiup list tidb`.
+        The command downloads a version cluster to the local machine and starts it, such as v6.1.7. To view the latest version, run `tiup list tidb`.
 
         This command returns the access methods of the cluster:
 

scale-tidb-using-tiup.md

@@ -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.10.0/cluster display <cluster-name>
     TiDB Cluster: <cluster-name>
-    TiDB Version: v6.1.6
+    TiDB Version: v6.1.7
     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

ticdc/manage-ticdc.md

@@ -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 v6.1.6.
+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 v6.1.7.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
 tiup update --self && \
 tiup update --all && \
-tiup cluster upgrade <cluster-name> v6.1.6
+tiup cluster upgrade <cluster-name> v6.1.7
 ```
 
 ### Notes for upgrade

tidb-binlog/get-started-with-tidb-binlog.md

@@ -42,7 +42,7 @@ sudo yum install -y mariadb-server
 ```
 
 ```bash
-curl -L https://download.pingcap.org/tidb-community-server-v6.1.6-linux-amd64.tar.gz | tar xzf -
+curl -L https://download.pingcap.org/tidb-community-server-v6.1.7-linux-amd64.tar.gz | tar xzf -
 cd tidb-latest-linux-amd64
 ```
 

tiflash/create-tiflash-replicas.md

@@ -155,7 +155,7 @@ Before TiFlash replicas are added, each TiKV instance performs a full table scan
    > In the preceding command, you need to replace `<CLUSTER_VERSION>` with the actual cluster version and `<PD_ADDRESS>:2379` with the address of any PD node. For example:
    >
    > ```shell
-   > tiup ctl:v6.1.6 pd -u http://192.168.1.4:2379 store limit all engine tiflash 60 add-peer
+   > tiup ctl:v6.1.7 pd -u http://192.168.1.4:2379 store limit all engine tiflash 60 add-peer
    > ```
 
    Within a few minutes, you will observe a significant increase in CPU and disk IO resource usage of the TiFlash nodes, and TiFlash should create replicas faster. At the same time, the TiKV nodes' CPU and disk IO resource usage increases as well.

tiup/tiup-cluster.md

@@ -118,20 +118,20 @@ tidb_servers:
 ...
 ```
 
-Save the file as `/tmp/topology.yaml`. If you want to use TiDB v6.1.6 and your cluster name is `prod-cluster`, run the following command:
+Save the file as `/tmp/topology.yaml`. If you want to use TiDB v6.1.7 and your cluster name is `prod-cluster`, run the following command:
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster deploy -p prod-cluster v6.1.6 /tmp/topology.yaml
+tiup cluster deploy -p prod-cluster v6.1.7 /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: v6.1.6
+TiDB Version: v6.1.7
 Type        Host          Ports        Directories
 ----        ----          -----        -----------
 pd          172.16.5.134  2379/2380    deploy/pd-2379,data/pd-2379
@@ -171,7 +171,7 @@ tiup cluster list
 Starting /root/.tiup/components/cluster/v1.10.0/cluster list
 Name          User  Version    Path                                               PrivateKey
 ----          ----  -------    ----                                               ----------
-prod-cluster  tidb  v6.1.6    /root/.tiup/storage/cluster/clusters/prod-cluster  /root/.tiup/storage/cluster/clusters/prod-cluster/ssh/id_rsa
+prod-cluster  tidb  v6.1.7    /root/.tiup/storage/cluster/clusters/prod-cluster  /root/.tiup/storage/cluster/clusters/prod-cluster/ssh/id_rsa
 ```
 
 ## Start the cluster
@@ -201,7 +201,7 @@ tiup cluster display prod-cluster
 ```
 Starting /root/.tiup/components/cluster/v1.10.0/cluster display prod-cluster
 TiDB Cluster: prod-cluster
-TiDB Version: v6.1.6
+TiDB Version: v6.1.7
 ID                  Role        Host          Ports        Status     Data Dir              Deploy Dir
 --                  ----        ----          -----        ------     --------              ----------
 172.16.5.134:3000   grafana     172.16.5.134  3000         Up         -                     deploy/grafana-3000
@@ -272,7 +272,7 @@ tiup cluster display prod-cluster
 ```
 Starting /root/.tiup/components/cluster/v1.10.0/cluster display prod-cluster
 TiDB Cluster: prod-cluster
-TiDB Version: v6.1.6
+TiDB Version: v6.1.7
 ID                  Role        Host          Ports        Status     Data Dir              Deploy Dir
 --                  ----        ----          -----        ------     --------              ----------
 172.16.5.134:3000   grafana     172.16.5.134  3000         Up         -                     deploy/grafana-3000
@@ -380,12 +380,12 @@ Global Flags:
   -y, --yes               Skip all confirmations and assumes 'yes'
 ```
 
-For example, the following command upgrades the cluster to v6.1.6:
+For example, the following command upgrades the cluster to v6.1.7:
 
 {{< copyable "shell-regular" >}}
 
 ```bash
-tiup cluster upgrade tidb-test v6.1.6
+tiup cluster upgrade tidb-test v6.1.7
 ```
 
 ## Update configuration
@@ -567,11 +567,11 @@ tiup cluster audit
 Starting component `cluster`: /home/tidb/.tiup/components/cluster/v1.10.0/cluster audit
 ID      Time                       Command
 --      ----                       -------
-4BLhr0  2023-02-28T23:55:09+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.6 /tmp/topology.yaml
-4BKWjF  2023-02-28T23:36:57+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.6 /tmp/topology.yaml
-4BKVwH  2023-02-28T23:02:08+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.6 /tmp/topology.yaml
-4BKKH1  2023-02-28T16:39:04+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster destroy test
-4BKKDx  2023-02-28T16:36:57+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.6 /tmp/topology.yaml
+4BLhr0  2023-07-12T23:55:09+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.7 /tmp/topology.yaml
+4BKWjF  2023-07-12T23:36:57+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.7 /tmp/topology.yaml
+4BKVwH  2023-07-12T23:02:08+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.7 /tmp/topology.yaml
+4BKKH1  2023-07-12T16:39:04+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster destroy test
+4BKKDx  2023-07-12T16:36:57+08:00  /home/tidb/.tiup/components/cluster/v1.11.3/cluster deploy test v6.1.7 /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:

tiup/tiup-component-cluster-deploy.md

@@ -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 `v6.1.6`.
+- `<version>`: the version number of the TiDB cluster to deploy, such as `v6.1.7`.
 - `<topology.yaml>`: the prepared [topology file](/tiup/tiup-cluster-topology-reference.md).
 
 ## Options

tiup/tiup-component-cluster-patch.md

@@ -28,7 +28,7 @@ Before running the `tiup cluster patch` command, you need to pack the binary pac
 1. Determine the following variables:
 
     - `${component}`: the name of the component to be replaced (such as `tidb`, `tikv`, or `pd`).
-    - `${version}`: the version of the component (such as `v6.1.6`).
+    - `${version}`: the version of the component (such as `v6.1.7`).
     - `${os}`: the operating system (`linux`).
     - `${arch}`: the platform on which the component runs (`amd64`, `arm64`).
 

tiup/tiup-component-management.md

@@ -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 v6.1.6.
+Example 3: Use TiUP to install TiKV v6.1.7.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup install tikv:v6.1.6
+tiup install tikv:v6.1.7
 ```
 
 ## Upgrade components
@@ -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 v6.1.6.
+Example 1: Operate TiDB v6.1.7.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup tidb:v6.1.6
+tiup tidb:v6.1.7
 ```
 
 Example 2: Specify the tag with which TiKV operates.
@@ -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 v6.1.6.
+Example 1: Uninstall TiDB v6.1.7.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup uninstall tidb:v6.1.6
+tiup uninstall tidb:v6.1.7
 ```
 
 Example 2: Uninstall TiKV of all versions.

tiup/tiup-mirror.md

@@ -86,9 +86,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 v6.1.6` command to clone the v6.1.6 version of the TiDB component.
-    - Run the `tiup mirror clone <target-dir> --tidb v6.1.6 --tikv all` command to clone the v6.1.6 version of the TiDB component and all versions of the TiKV component.
-    - Run the `tiup mirror clone <target-dir> v6.1.6` command to clone the v6.1.6 version of all components in a cluster.
+    - Execute the `tiup mirror clone <target-dir> --tidb v6.1.7` command to clone the v6.1.7 version of the TiDB component.
+    - Run the `tiup mirror clone <target-dir> --tidb v6.1.7 --tikv all` command to clone the v6.1.7 version of the TiDB component and all versions of the TiKV component.
+    - Run the `tiup mirror clone <target-dir> v6.1.7` command to clone the v6.1.7 version of all components in a cluster.
 
 After cloning, signing keys are set up automatically.
 

tiup/tiup-playground.md

@@ -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.10.0, then this command works the same as `tiup playground:v1.10.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 v6.1.6, then this command works the same as `tiup playground:v1.10.0 v6.1.6`.
+- 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 v6.1.7, then this command works the same as `tiup playground:v1.10.0 v6.1.7`.
 - 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).
 

upgrade-tidb-using-tiup.md

@@ -169,12 +169,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 v6.1.6:
+For example, if you want to upgrade the cluster to v6.1.7:
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster upgrade <cluster-name> v6.1.6
+tiup cluster upgrade <cluster-name> v6.1.7
 ```
 
 > **Note:**
@@ -231,7 +231,7 @@ tiup cluster display <cluster-name>
 ```
 Cluster type:       tidb
 Cluster name:       <cluster-name>
-Cluster version:    v6.1.6
+Cluster version:    v6.1.7
 ```
 
 ## FAQ
@@ -277,5 +277,5 @@ You can upgrade the tool version by using TiUP to install the `ctl` component of
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup install ctl:v6.1.6
+tiup install ctl:v6.1.7
 ```