Can TiDB 4.0 be upgraded to 7.6?

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb4.0,可以升级到7.6吗

| username: TiDBer_D9HpHEkS

[TiDB Usage Environment] Production Environment
[TiDB Version] 4.0.0
[Reproduction Path]
[Encountered Problem: Problem Phenomenon and Impact] Currently using version 4.0.0 in production, is it compatible to upgrade to 7.6? Is there a need to upgrade? How to upgrade?
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

| username: WalterWj | Original post link

You need to transition through two intermediate versions. 使用 TiUP 升级 TiDB | PingCAP 文档中心

| username: TiDBer_D9HpHEkS | Original post link

My current TiDB 4.0 is managed and installed using TiUP.

| username: ShawnYan | Original post link

Necessary, version 4.0 is no longer maintained. If you encounter a bug that you can’t bypass, you’ll still need to upgrade. However, thorough testing is required.

| username: Kongdom | Original post link

Based on our own situation, we should upgrade to version v7.5.0. The performance improvements in all aspects are quite significant.

| username: Jellybean | Original post link

If you need to upgrade, it is recommended to deploy another v7.5 version cluster and use a synchronized upgrade method to switch the business.

It is not recommended to directly upgrade on a single cluster.

| username: 随缘天空 | Original post link

If there are no issues during use, it is not recommended to upgrade; otherwise, you might be blamed for any errors. Additionally, make sure to document everything before upgrading and try to back up the data. Do not upgrade directly to version 7.6; instead, upgrade to major versions 5 and 6 first before moving to 7.6.

| username: 哈喽沃德 | Original post link

The version gap is too large, it would be better to deploy a new environment and then perform data migration.

| username: changpeng75 | Original post link

Deploy a new environment and use TiCDC for incremental synchronization.

| username: zhanggame1 | Original post link

7.6 is a test version, 7.5 can be upgraded, but since the version gap is too large, it’s better to install a new one and migrate the data.

| username: 数据库真NB | Original post link

  1. It is not recommended to upgrade directly to V7; upgrading one version at a time is more reliable.
  2. If possible, run dual tracks.
| username: 江湖故人 | Original post link

Version 7.6 is a DMR version and cannot be used in a production environment. It is recommended to migrate to version 7.5, as the upgrade path is less common and more likely to encounter issues.

| username: dba-kit | Original post link

The description is consistent with the above-mentioned suggestions to upgrade to 7.5 through migrating the cluster. Upgrading from 4.0 to 7.5 will bring substantial improvements in both performance and operability.

| username: TIDB-Learner | Original post link

Do not upgrade to the test version in the production environment.

| username: dockerfile | Original post link

The consequences of not upgrading for a long time.

  1. First, upgrade to 5.2 to get accustomed to the new features and operational methods.
  2. Then, choose an appropriate time to upgrade to 7.1.x or 7.5.x.
| username: dba远航 | Original post link

I feel the risk is relatively high.

| username: wangccsy | Original post link

It feels like quite a big leap.

| username: 这里介绍不了我 | Original post link

Gradually increase

| username: kelvin | Original post link

The version gap is too large. I suggest deploying a new environment before migrating.

| username: zhaokede | Original post link

First, verify the business in the test environment before upgrading, as upgrading carries risks.