Compatibility between TiDB-V5.2.1 Cluster and V6.1.0 Version

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

Original topic: TIDB-V5.2.1集群和V6.1.0版兼容性

| username: TiDBer_cxPOfHmI

【TiDB Usage Environment】Production environment
【TiDB Version】Current version V5.2.1
【Encountered Problem】Currently, we need to set up a new TiDB cluster with version V6.1.0 and migrate the data from the old cluster to the new one. The old cluster will be used for data backup. Are the old V5.2.1 and new V6.1.0 versions compatible? Will it affect the operation of the two clusters?

| username: TiDBer_cxPOfHmI | Original post link

Seeking an answer, urgent urgent urgent

| username: xiaohetao | Original post link

Are you currently encountering any issues?

| username: Kongdom | Original post link

Previously, I wrote a bit about it, just for reference. Pay special attention to point 5

| username: xiaohetao | Original post link

:+1::+1::+1::+1:

| username: TiDBer_cxPOfHmI | Original post link

It’s not about upgrading the existing cluster, but rather setting up a new cluster with version V6.1.0 and backing up data from the original V5.2.1 cluster. Will there be any issues due to differences between the two versions?

| username: Kongdom | Original post link

So these are two independent clusters. How can they affect each other?

| username: TiDBer_cxPOfHmI | Original post link

Will there be compatibility issues if the new cluster provides external services while the old cluster handles data synchronization and backup, given that the versions are inconsistent?

| username: Kongdom | Original post link

No, TiDB supports synchronization with other databases, so how could it not support synchronization with its own database?

| username: TiDBer_cxPOfHmI | Original post link

Currently conducting research, if there are compatibility issues with the version, we will consider installing the same version as the existing cluster.

| username: TiDBer_cxPOfHmI | Original post link

If a new TiDB cluster is created, should it be consistent with the current cluster version or use the latest version? (The current version is V5.2.1)

| username: Kongdom | Original post link

Suggest maintaining consistency~

| username: forever | Original post link

If considering the compatibility of the program after data upgrade, the experts have already mentioned it. If it’s just for a delayed standby machine, then compatibility mainly involves basic operations like insert, delete, and update, and shouldn’t involve SQL queries and features, so compatibility issues are minimal as long as the synchronization tool supports it. If it also involves disaster recovery switching, then the program needs to support both versions. However, if you want to do something similar to MySQL’s standby machine, that’s definitely not feasible, as even br backup in the old cluster does not support cross-version.