Bug #107032 | The upgrade speed is slow and when there are a large number of partition tables. | ||
---|---|---|---|
Submitted: | 15 Apr 2022 6:42 | Modified: | 15 Apr 2022 13:25 |
Reporter: | jiwei zhangjiwei | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[15 Apr 2022 6:42]
jiwei zhangjiwei
[15 Apr 2022 7:27]
jiwei zhangjiwei
The problem is introduced on commit 9162689906544c59ffea6af88d5686238755018b
[15 Apr 2022 13:25]
MySQL Verification Team
Hi Mr. zhangjiwei, Thank you for your bug report. However, it is not a bug. Simply, there were changes in the structure of the partition tables between 8.0.18 and 8.0.28, so that each partition has to be upgraded in order to work properly with 8.0.28 and later releases. If we would skip calling that function for each partition, your installation could have experienced possible corruption of data. We the upgrade that we designed, you have to wait for it to finish and your installation is ready for production. In this manner, each partition is upgraded and you will not encounter corruption nor other heavy problems. Not a bug.
[15 Apr 2022 16:32]
cheng zhao
In test, 50,000 partitions use 5mins to upgrade and 1000,000 partitions use 2hours. During the process, mysql.innodb_datafiles,mysql.innodb_tablespaces,mysql.innodb_table_stats and mysql.innodb_index_stats are updated. The modification of innodb_datafiles and innodb_tablespaces is committd per 10000 partitions, while modification of innodb_table_stats and innodb_index_stats is committed per partition. Could the process of updating innodb_table_stats and innodb_index_stats be improved like innodb_datafiles and innodb_tablespaces?