Skip to content

Commit 7c8615b

Browse files
authored
tiflash: Update tiflash upgrade guide (#21619) (#21625)
1 parent 82e1fc7 commit 7c8615b

File tree

1 file changed

+16
-5
lines changed

1 file changed

+16
-5
lines changed

tiflash-upgrade-guide.md

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ If you do not enable [dynamic pruning mode](/partitioned-table.md#dynamic-prunin
8282

8383
## From v5.x or v6.0 to v6.2
8484

85-
In TiDB v6.2, TiFlash upgrades its data storage format to the V3 version. Therefore, when you upgrade TiFlash from v5.x or v6.0 to v6.2, besides functional changes in [TiFlash Proxy](#tiflash-proxy) and [Dynamic pruning](#dynamic-pruning), you also need to pay attention to the functional change in PageStorage.
85+
In TiDB v6.2, TiFlash upgrades its data storage format to V3 to reduce write amplification and improve TiFlash stability. When you upgrade from v5.x, v6.0, or v6.1 to v6.2 or a later version, in addition to the functional changes in [TiFlash Proxy](#tiflash-proxy) and [Dynamic pruning](#dynamic-pruning), you also need to pay attention to the functional change in PageStorage.
8686

8787
### PageStorage
8888

@@ -105,14 +105,25 @@ You can check whether tables still use the old data format on Grafana: **TiFlash
105105
- Only V3: Number of tables using PageStorage V3 (including partitions)
106106
- Mix Mode: Number of tables with data format converted from PageStorage V2 to PageStorage V3 (including partitions)
107107

108+
> **Note:**
109+
>
110+
> The following patch versions have a known issue (Issue [#9039](https://github.com/pingcap/tiflash/issues/9039)). Upgrading to these versions might cause TiFlash data corruption.
111+
>
112+
> - v6.5.0 to v6.5.9
113+
> - v6.6.0
114+
> - v7.0.0
115+
> - v7.1.0 to v7.1.5
116+
> - v7.2.0
117+
> - v7.3.0
118+
> - v7.4.0
119+
> - v7.5.0 to v7.5.1
120+
>
121+
> It is recommended that you upgrade to v6.5.10, v7.1.6, v7.5.2, or a later version where this issue has been fixed.
122+
108123
**Workaround for downgrading TiFlash in testing or other special scenarios**
109124

110125
You can forcibly scale in the target TiFlash node and then replicate data from TiKV again. For detailed steps, see [Scale in a TiFlash cluster](/scale-tidb-using-tiup.md#scale-in-a-tiflash-cluster).
111126

112-
## From v6.1 to v6.2
113-
114-
When you upgrade TiFlash from v6.1 to v6.2, pay attention to the change in data storage format. For details, see [PageStorage](#pagestorage).
115-
116127
## From v6.x or v7.x to v7.3 with `storage.format_version = 5` configured
117128

118129
Starting from v7.3, TiFlash introduces a new DTFile version: DTFile V3 (experimental). This new DTFile version can merge multiple small files into a single larger file to reduce the total number of files. In v7.3, the default DTFile version is still V2. To use V3, you can set the [TiFlash configuration parameter](/tiflash/tiflash-configuration.md) `storage.format_version = 5`. After the setting, TiFlash can still read V2 DTFiles and will gradually rewrite existing V2 DTFiles to V3 DTFiles during subsequent data compaction.

0 commit comments

Comments
 (0)