pingcap · ti-chi-bot · Jun 10, 2021 · Jun 1, 2021 · Jun 1, 2021 · Jun 2, 2021
diff --git a/TOC.md b/TOC.md
@@ -539,6 +539,7 @@
 + Release Notes
   + [All Releases](/releases/release-notes.md)
   + v5.0
+    + [5.0.2](/releases/release-5.0.2.md)
     + [5.0.1](/releases/release-5.0.1.md)
     + [5.0 GA](/releases/release-5.0.0.md)
     + [5.0.0-rc](/releases/release-5.0.0-rc.md)

diff --git a/download-ecosystem-tools.md b/download-ecosystem-tools.md
@@ -17,7 +17,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.0.0` is `https://download.pingcap.org/tidb-v5.0.0-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v5.0.2` is `https://download.pingcap.org/tidb-v5.0.2-linux-amd64.tar.gz`.
 
 ## TiDB Lightning
 
@@ -29,7 +29,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.0.0` is `https://download.pingcap.org/tidb-toolkit-v5.0.0-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of TiDB Lightning. For example, the download link for `v5.0.2` is `https://download.pingcap.org/tidb-toolkit-v5.0.2-linux-amd64.tar.gz`.
 
 ## BR (backup and restore)
 
@@ -41,7 +41,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.0.0-beta` is `http://download.pingcap.org/tidb-toolkit-v5.0.0-beta-linux-amd64.tar.gz`.
+> `{version}` in the above download link indicates the version number of BR. For example, the download link for `v5.0.2` is `http://download.pingcap.org/tidb-toolkit-v5.0.2-linux-amd64.tar.gz`.
 
 ## TiDB DM (Data Migration)
 
@@ -53,7 +53,7 @@ Download [DM](https://docs.pingcap.com/tidb-data-migration/v1.0/overview) by usi
 
 > **Note:**
 >
-> `{version}` in the above download link indicates the version number of DM. For example, the download link for `v2.0.1` is `https://download.pingcap.org/dm-v2.0.1-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 `v2.0.3` is `https://download.pingcap.org/dm-v2.0.3-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/dm/releases) page.
 
 ## Dumpling
 
@@ -65,7 +65,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 `v4.0.11` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v4.0.11-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.0.2` version of Dumpling is `https://download.pingcap.org/tidb-toolkit-v5.0.2-linux-amd64.tar.gz`. You can view the currently released versions in [Dumpling Releases](https://github.com/pingcap/dumpling/releases).
 >
 > Dumpling supports arm64 linux. You can replace `amd64` in the download link with `arm64`, which means the `arm64` version of Dumpling.
 

diff --git a/pd-recover.md b/pd-recover.md
@@ -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.0.0`, the package download link is `https://download.pingcap.org/tidb-v5.0.0-linux-amd64.tar.gz`.
+> `{version}` indicates the version number of TiDB. For example, if `{version}` is `v5.0.2`, the package download link is `https://download.pingcap.org/tidb-v5.0.2-linux-amd64.tar.gz`.
 
 ## Quick Start
 

diff --git a/production-deployment-using-tiup.md b/production-deployment-using-tiup.md
@@ -260,13 +260,13 @@ Then execute the `deploy` command to deploy the TiDB cluster:
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster deploy tidb-test v5.0.0 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
+tiup cluster deploy tidb-test v5.0.2 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]
 ```
 
 In the above command:
 
 - The name of the deployed TiDB cluster is `tidb-test`.
-- You can see the latest supported versions by running `tiup list tidb`. This document takes `v5.0.0` as an example.
+- You can see the latest supported versions by running `tiup list tidb`. This document takes `v5.0.2` as an example.
 - The initialization configuration file is `topology.yaml`.
 - `--user root`: Log in to the target machine through the `root` key to complete the cluster deployment, or you can use other users with `ssh` and `sudo` privileges to complete the deployment.
 - `[-i]` and `[-p]`: 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.
@@ -288,7 +288,7 @@ TiUP supports managing multiple TiDB clusters. The command above outputs informa
 Starting /home/tidb/.tiup/components/cluster/v1.3.0/cluster list
 Name              User  Version        Path                                                        PrivateKey
 ----              ----  -------        ----                                                        ----------
-tidb-test         tidb  v5.0.0      /home/tidb/.tiup/storage/cluster/clusters/tidb-test         /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa
+tidb-test         tidb  v5.0.2      /home/tidb/.tiup/storage/cluster/clusters/tidb-test         /home/tidb/.tiup/storage/cluster/clusters/tidb-test/ssh/id_rsa
 ```
 
 ## Step 6: Check the status of the deployed TiDB cluster

diff --git a/quick-start-with-tidb.md b/quick-start-with-tidb.md
@@ -55,10 +55,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
         {{< copyable "shell-regular" >}}
 
         ```shell
-        tiup playground v5.0.1 --db 2 --pd 3 --kv 3 --monitor
+        tiup playground v5.0.2 --db 2 --pd 3 --kv 3 --monitor
         ```
 
-        The command downloads a version cluster to the local machine and starts it, such as v5.0.1. `--monitor` means that the monitoring component is also deployed.
+        The command downloads a version cluster to the local machine and starts it, such as v5.0.2. `--monitor` means that the monitoring component is also deployed.
 
         To view the latest version, run `tiup list tidb`.
 
@@ -160,10 +160,10 @@ As a distributed system, a basic TiDB test cluster usually consists of 2 TiDB in
         {{< copyable "shell-regular" >}}
 
         ```shell
-        tiup playground v5.0.1 --db 2 --pd 3 --kv 3 --monitor
+        tiup playground v5.0.2 --db 2 --pd 3 --kv 3 --monitor
         ```
 
-        The command downloads a version cluster to the local machine and starts it, such as v5.0.1. `--monitor` means that the monitoring component is also deployed.
+        The command downloads a version cluster to the local machine and starts it, such as v5.0.2. `--monitor` means that the monitoring component is also deployed.
 
         To view the latest version, run `tiup list tidb`.
 

diff --git a/releases/release-5.0.2.md b/releases/release-5.0.2.md
@@ -0,0 +1,131 @@
+---
+title: TiDB 5.0.2 Release Notes
+---
+
+# TiDB 5.0.2 Release Notes
+
+Release date: June 10, 2021
+
+TiDB version: 5.0.2
+
+## Compatibility Changes
+
++ Tools
+
+    + TiCDC
+
+        - Deprecate `--sort-dir` in the `cdc cli changefeed` command. Instead, users can set `--sort-dir` in the `cdc server` command. [#1795](https://github.com/pingcap/ticdc/pull/1795)
+
+## New Features
+
++ TiKV
+
+    - Enable the Hibernate Region feature by default [#10266](https://github.com/tikv/tikv/pull/10266)
+
+## Improvements
+
++ TiDB
+
+    - Avoid frequently reading the `mysql.stats_histograms` table if the cached statistics is up-to-date to avoid high CPU usage [#24317](https://github.com/pingcap/tidb/pull/24317)
+
++ TiKV
+
+    - BR now supports the S3-compatible storage using the virtual-host addressing mode [#10243](https://github.com/tikv/tikv/pull/10243)
+    - Support the back pressure for TiCDC's scan speed [#10151](https://github.com/tikv/tikv/pull/10151)
+    - Reduce the memory usage of TiCDC's initial scan [#10133](https://github.com/tikv/tikv/pull/10133)
+    - Improve the cache hit ratio of the TiCDC's Old Value feature in the pessimistic transaction [#10089](https://github.com/tikv/tikv/pull/10089)
+    - Split Regions more evenly [#10086](https://github.com/tikv/tikv/pull/10086)
+
++ TiFlash
+
+    - Optimize the table lock to prevent DDL jobs and data reads from blocking each other
+    - Support casting the `INTEGER` or `REAL` type to `REAL` type
+
++ Tools
+
+    + TiCDC
+
+        - Add monitoring metrics for the table memory consumption [#1885](https://github.com/pingcap/ticdc/pull/1885)
+        - Optimize the memory and CPU usages during the sorting stage [#1863](https://github.com/pingcap/ticdc/pull/1863)
+        - Delete some useless log information that might cause user confusion [#1759](https://github.com/pingcap/ticdc/pull/1759)
+
+    + Backup & Restore (BR)
+
+        - Clarify some ambiguous error messages [#1132](https://github.com/pingcap/br/pull/1132)
+        - Support checking the cluster version of a backup [#1091](https://github.com/pingcap/br/pull/1091)
+        - Support backing up and restoring system tables in the `mysql` schema [#1143](https://github.com/pingcap/br/pull/1143) [#1078](https://github.com/pingcap/br/pull/1078)
+
+    + Dumpling
+
+        - Fix the issue that no error is output when a backup operation fails [#280](https://github.com/pingcap/dumpling/pull/280)
+
+## Bug Fixes
+
++ TiDB
+
+    - Fix the panic issue caused by using the prefix index and index join in some cases [#24547](https://github.com/pingcap/tidb/issues/24547) [#24716](https://github.com/pingcap/tidb/issues/24716) [#24717](https://github.com/pingcap/tidb/issues/24717)
+    - Fix the issue that the prepared plan cache of `point get` is incorrectly used by the `point get` statement in the transaction [#24741](https://github.com/pingcap/tidb/issues/24741)
+    - Fix the issue of writing the wrong prefix index value when the collation is `ascii_bin` or `latin1_bin` [#24569](https://github.com/pingcap/tidb/issues/24569)
+    - Fix the issue that the ongoing transaction might be interrupted by the GC worker [#24591](https://github.com/pingcap/tidb/issues/24591)
+    - Fix a bug that the point query might get wrong on the clustered index when `new-collation` is enabled but `new-row-format` is disabled [#24541](https://github.com/pingcap/tidb/issues/24541)
+    - Refactor the conversion of partition keys for shuffle hash join [#24490](https://github.com/pingcap/tidb/pull/24490)
+    - Fix the panic issue that occurs when building the plan for queries that contain the `HAVING` clause [#24045](https://github.com/pingcap/tidb/issues/24045)
+    - Fix the issue that the column pruning improvement causes the `Apply` and `Join` operators' results to go wrong [#23887](https://github.com/pingcap/tidb/issues/23887)
+    - Fix a bug that the primary lock fallen back from async commit cannot be resolved [#24384](https://github.com/pingcap/tidb/issues/24384)
+    - Fix a GC issue of statistics that might cause duplicated fm-sketch records [#24357](https://github.com/pingcap/tidb/pull/24357)
+    - Avoid unnecessary pessimistic rollback when the pessimistic locking receives the `ErrKeyExists` error [#23799](https://github.com/pingcap/tidb/issues/23799)
+    - Fix the issue that numeric literals cannot be recognized when the sql_mode contains `ANSI_QUOTES` [#24522](https://github.com/pingcap/tidb/pull/24522)
+    - Forbid statements such as `INSERT INTO table PARTITION (<partitions>) ... ON DUPLICATE KEY UPDATE` to read data from non-listed partitions [#24746](https://github.com/pingcap/tidb/issues/24746)
+    - Fix the potential `index out of range` error when a SQL statement contains both `GROUP BY` and `UNION` [#24281](https://github.com/pingcap/tidb/issues/24281)
+    - Fix the issue that the `CONCAT` function incorrectly handles the collation [#24296](https://github.com/pingcap/tidb/issues/24296)
+    - Fix the issue that the `collation_server` global variable does not take effect in new sessions [#24156](https://github.com/pingcap/tidb/pull/24156)
+
++ TiKV
+
+    - Fix a TiCDC OOM issue caused by reading old values [#9996](https://github.com/tikv/tikv/issues/9996) [#9981](https://github.com/tikv/tikv/issues/9981)
+    - Fix the issue of empty value in the secondary index for the clustered primary key column when collation is `latin1_bin` [#24548](https://github.com/pingcap/tidb/issues/24548)
+    - Add the `abort-on-panic` configuration, which allows TiKV to generate the core dump file when panic occurs. Users still need to correctly configure the environment to enable core dump [#10216](https://github.com/tikv/tikv/pull/10216)
+    - Fix the performance regression issue of `point get` queries that occurs when TiKV is not busy [#10046](https://github.com/tikv/tikv/issues/10046)
+
++ PD
+
+    - Fix the issue that the PD Leader re-election is slow when there are many stores [#3697](https://github.com/tikv/pd/issues/3697)
+    - Fix the panic issue that occurs when removing the evict leader scheduler from a non-existent store [#3660](https://github.com/tikv/pd/issues/3660)
+    - Fix the issue that the statistics are not updated after offline peers are merged [#3611](https://github.com/tikv/pd/issues/3611)
+
++ TiFlash
+
+    - Fix the issue of incorrect results when cloning shared delta index concurrently
+    - Fix the potential issue that TiFlash fails to restart with incomplete data
+    - Fix the issue that old dm files are not removed automatically
+    - Fix the potential panic that occurs when the Compaction Filter feature is enabled
+    - Fix the potential issue that `ExchangeSender` sends duplicated data
+    - Fix the issue that TiFlash cannot resolve the lock fallen back from async commit
+    - Fix the issue of incorrect results returned when the casted result of the `TIMEZONE` type contains the `TIMESTAMP` type
+    - Fix the TiFlash panic issue that occurs during Segment Split
+    - Fix the issue that the execution information about the non-root MPP task is not accurate
+
++ Tools
+
+    + TiCDC
+
+        - Fix the issue that the time zone information is lost in the Avro output [#1712](https://github.com/pingcap/ticdc/pull/1712)
+        - Support cleaning up stale temporary files in Unified Sorter and forbid sharing the `sort-dir` directory [#1742](https://github.com/pingcap/ticdc/pull/1742)
+        - Fix a deadlock bug in the KV client that occurs when many stale Regions exist [#1801](https://github.com/pingcap/ticdc/pull/1801)
+        - Fix the wrong help information in the `--cert-allowed-cn` flag [#1697](https://github.com/pingcap/ticdc/pull/1697)
+        - Revert the update for `explicit_defaults_for_timestamp` which requires the `SUPER` privilege when replicating data to MySQL [#1750](https://github.com/pingcap/ticdc/pull/1750)
+        - Support the sink flow control to reduce the risk of memory overflow [#1840](https://github.com/pingcap/ticdc/pull/1840)
+        - Fix a bug that the replication task might stop when moving a table [#1828](https://github.com/pingcap/ticdc/pull/1828)
+        - Fix the issue that the TiKV GC safe point is blocked due to the stagnation of TiCDC changefeed checkpoint [#1759](https://github.com/pingcap/ticdc/pull/1759)
+
+    + Backup & Restore (BR)
+
+        - Fix the issue that the `DELETE` events are lost during the log restore [#1063](https://github.com/pingcap/br/issues/1063)
+        - Fix a bug that causes BR to send too many useless RPC requests to TiKV [#1037](https://github.com/pingcap/br/pull/1037)
+        - Fix the issue that no error is output when a backup operation fails [#1043](https://github.com/pingcap/br/pull/1043)
+
+    + TiDB Lightning
+
+        - Fix the issue of TiDB Lightning panic that occurs when generating KV data [#1127](https://github.com/pingcap/br/pull/1127)
+        - Fix the issue that TiDB Lightning in the TiDB-backend mode cannot load any data when the autocommit is disabled [#1104](https://github.com/pingcap/br/issues/1104)
+        - Fix a bug that the batch split Region fails due to the total key size exceeding the raft entry limit during the data import [#969](https://github.com/pingcap/br/issues/969)
diff --git a/releases/release-notes.md b/releases/release-notes.md
@@ -6,6 +6,7 @@ title: Release Notes
 
 ## 5.0
 
+- [5.0.2](/releases/release-5.0.2.md)
 - [5.0.1](/releases/release-5.0.1.md)
 - [5.0 GA](/releases/release-5.0.0.md)
 - [5.0.0-rc](/releases/release-5.0.0-rc.md)

diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md
@@ -257,7 +257,7 @@ If you want to remove a TiKV node from the `10.0.1.5` host, take the following s
     ```
     Starting /root/.tiup/components/cluster/v1.3.0/cluster display <cluster-name>
     TiDB Cluster: <cluster-name>
-    TiDB Version: v5.0.0
+    TiDB Version: v5.0.2
     ID              Role         Host        Ports                            Status  Data Dir                Deploy Dir
     --              ----         ----        -----                            ------  --------                ----------
     10.0.1.3:8300   cdc          10.0.1.3    8300                             Up      -                       deploy/cdc-8300

diff --git a/ticdc/manage-ticdc.md b/ticdc/manage-ticdc.md
@@ -9,14 +9,14 @@ This document describes how to manage the TiCDC cluster and replication tasks us
 
 ## 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 v4.0.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 v5.0.2.
 
 {{< copyable "shell-regular" >}}
 
 ```shell
 tiup update --self && \
 tiup update --all && \
-tiup cluster upgrade <cluster-name> v4.0.6
+tiup cluster upgrade <cluster-name> v5.0.2
 ```
 
 ### Notes for upgrade

diff --git a/tiup/tiup-component-cluster-deploy.md b/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 `v4.0.9`.
+- `<version>`: the version number of the TiDB cluster to deploy, such as `v5.0.2`.
 - `<topology.yaml>`: the prepared [topology file](/tiup/tiup-cluster-topology-reference.md).
 
 ## Options

diff --git a/upgrade-tidb-using-tiup.md b/upgrade-tidb-using-tiup.md
@@ -149,12 +149,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.0.0:
+For example, if you want to upgrade the cluster to v5.0.2:
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup cluster upgrade <cluster-name> v5.0.0
+tiup cluster upgrade <cluster-name> v5.0.2
 ```
 
 > **Note:**
@@ -204,7 +204,7 @@ tiup cluster display <cluster-name>
 ```
 Cluster type:       tidb
 Cluster name:       <cluster-name>
-Cluster version:    v5.0.0
+Cluster version:    v5.0.2
 ```
 
 > **Note:**
@@ -254,7 +254,7 @@ You can upgrade the tool version by using TiUP to install the `ctl` component of
 {{< copyable "shell-regular" >}}
 
 ```shell
-tiup install ctl:v5.0.0
+tiup install ctl:v5.0.2
 ```
 
 ## TiDB 5.0 compatibility changes